Triple
T35724540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninian Pipeline System |
E1032569
|
entity |
| Predicate | locatedOnShelf |
P206024
|
FINISHED |
| Object | UK sector of the North Sea |
—
|
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: UK sector of the North Sea | Statement: [Ninian Pipeline System, locatedOnShelf, UK sector of the North Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnShelf Context triple: [Ninian Pipeline System, locatedOnShelf, UK sector of the North Sea]
-
A.
hasShelfPlacement
Indicates the specific location or position an item occupies on a shelf.
-
B.
libraryLocation
Indicates the physical or organizational place where a library or its resources are situated.
-
C.
shelfMark
Indicates the classification or call number assigned to an item to specify its exact location on a shelf or within a storage system.
-
D.
locatedOnLevel
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
-
E.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
- F. None of above. chosen
Provenance (4 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:05 p.m.