Triple
T87744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourne Bridge |
E1763
|
entity |
| Predicate | hasClearanceBelow |
P4064
|
FINISHED |
| Object | about 135 feet |
—
|
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: about 135 feet | Statement: [Bourne Bridge, hasClearanceBelow, about 135 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClearanceBelow Context triple: [Bourne Bridge, hasClearanceBelow, about 135 feet]
-
A.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
C.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
-
E.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a2503d304c8190a0034ffa4a38a501 |
completed | Feb. 28, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69a24eb6da2c8190a33d144d219f7abe |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a2503c12808190a3cbb7b171f466f0 |
completed | Feb. 28, 2026, 2:17 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.