Triple
T1893594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunnel Log |
E41926
|
entity |
| Predicate | hasApproxTunnelLength |
P12895
|
FINISHED |
| Object | about 17 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 17 feet | Statement: [Tunnel Log, hasApproxTunnelLength, about 17 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproxTunnelLength Context triple: [Tunnel Log, hasApproxTunnelLength, about 17 feet]
-
A.
hasTunnelLengthApprox
chosen
Indicates that an entity has a tunnel whose length is approximately a specified value.
-
B.
hasTunnel
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
C.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
D.
tunnelCircumference
Indicates the circular distance around the inner boundary of a tunnel’s cross-section.
-
E.
usesTunnel
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb1497df08190ad90dd89f76208ca |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.