Triple
T6221573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Nova |
E139125
|
entity |
| Predicate | productionFacilityLocation |
P27029
|
FINISHED |
| Object | moored on the Grand Banks |
—
|
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: moored on the Grand Banks | Statement: [Terra Nova, productionFacilityLocation, moored on the Grand Banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionFacilityLocation Context triple: [Terra Nova, productionFacilityLocation, moored on the Grand Banks]
-
A.
locationOfFacility
chosen
Indicates that a facility is situated at or associated with a specific geographic location.
-
B.
mainManufacturingSite
Indicates the primary location where an entity’s products are manufactured or produced.
-
C.
firstMajorProductionLocation
Indicates the location where an entity’s first major production or large-scale manufacturing activity took place.
-
D.
sisterFacilityLocation
Indicates that one facility is located in the same or a corresponding place as another facility with which it has a sister or peer relationship.
-
E.
trainingFacilityLocation
Indicates the place or site where a training facility is situated or operates.
- 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.