Triple
T5332504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sellin |
E123341
|
entity |
| Predicate | hasPierLength |
P62876
|
FINISHED |
| Object | approximately 394 metres |
—
|
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: approximately 394 metres | Statement: [Sellin, hasPierLength, approximately 394 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPierLength Context triple: [Sellin, hasPierLength, approximately 394 metres]
-
A.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
B.
hasNumberOfPiersInWater
Indicates the quantity of piers that extend into or are situated within a body of water.
-
C.
hasPierFunction
Indicates that an entity serves the role or function of a pier, such as providing a structure that extends over water for access, docking, or related activities.
-
D.
hasBerthDepth
Indicates the depth of water available at a specific berth where a vessel can be moored.
-
E.
hasSkyBridgeLength
Indicates the length measurement of a sky bridge connecting two structures or areas.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85aab0308190990626cbc9da3e21 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8501d53c81908371bd5195ba5703 |
completed | March 20, 2026, 5:33 p.m. |
Created at: March 20, 2026, 2 p.m.