Triple
T6221556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Nova |
E139125
|
entity |
| Predicate | developmentConcept |
P41845
|
FINISHED |
| Object | subsea wells tied back to FPSO |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: subsea wells tied back to FPSO | Statement: [Terra Nova, developmentConcept, subsea wells tied back to FPSO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentConcept Context triple: [Terra Nova, developmentConcept, subsea wells tied back to FPSO]
-
A.
featuredConcept
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
-
B.
development
Indicates a process or relationship in which something grows, advances, or becomes more complex or mature over time.
-
C.
developmentMethod
chosen
Indicates the process, technique, or approach used to create, build, or evolve something.
-
D.
technologyConcept
Indicates a relationship where one entity represents or embodies a technological idea, principle, or method conceptually associated with another entity.
-
E.
developmentFunction
Indicates a relationship where one entity serves as a function, role, or mechanism that drives, supports, or shapes the development or growth of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062bddb688190add53172a7445d01 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.