Triple
T34171825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotherhithe Tunnel |
E876564
|
entity |
| Predicate | hasWidthLimit |
P3989
|
FINISHED |
| Object | 2.0 m |
—
|
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: 2.0 m | Statement: [Rotherhithe Tunnel, hasWidthLimit, 2.0 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWidthLimit Context triple: [Rotherhithe Tunnel, hasWidthLimit, 2.0 m]
-
A.
hasLimitSet
Indicates that there is a defined boundary, range, or constraint applied to something.
-
B.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
C.
hasWidth
chosen
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
D.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
E.
hasWidthRange
Indicates that an entity’s width falls within a specified minimum-to-maximum range.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:54 a.m.