Triple
T34171824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotherhithe Tunnel |
E876564
|
entity |
| Predicate | hasHeightLimit |
P9788
|
FINISHED |
| Object | 1.9 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: 1.9 m | Statement: [Rotherhithe Tunnel, hasHeightLimit, 1.9 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeightLimit Context triple: [Rotherhithe Tunnel, hasHeightLimit, 1.9 m]
-
A.
heightRestriction
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
B.
heightRestrictionWithCompanion
Indicates that there is a height-based restriction which may be satisfied or modified when the person is accompanied by a qualifying companion.
-
C.
heightUpperBound
Indicates that one entity’s height serves as an upper limit or maximum allowable height for another entity.
-
D.
hasHeight
chosen
Indicates that one entity possesses a specific vertical measurement or stature.
-
E.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
- 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_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:54 a.m.