Triple
T30953530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilbury Ferry |
E788609
|
entity |
| Predicate | hasPierStructure |
P15921
|
FINISHED |
| Object | Tilbury Town Pier |
—
|
NE NERFINISHED |
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: Tilbury Town Pier | Statement: [Tilbury Ferry, hasPierStructure, Tilbury Town Pier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPierStructure Context triple: [Tilbury Ferry, hasPierStructure, Tilbury Town Pier]
-
A.
hasPier
chosen
Indicates that a location or structure possesses or includes a pier as part of its features.
-
B.
hasPiersOn
Indicates that one structure or location is supported or extended by piers that are physically situated on another structure or surface.
-
C.
hasPierLength
Indicates that one entity (typically a pier or similar structure) has a specified length measurement.
-
D.
hasPierUse
Indicates that something is used as, or functions in the role of, a pier.
-
E.
hasNumberOfPiersInWater
Indicates the quantity of piers that extend into or are situated within a body of water.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:53 p.m.