Triple
T8824077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer Cabin Tree |
E209970
|
entity |
| Predicate | tunnelUsedBy |
P18707
|
FINISHED |
| Object | pedestrians |
—
|
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: pedestrians | Statement: [Pioneer Cabin Tree, tunnelUsedBy, pedestrians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelUsedBy Context triple: [Pioneer Cabin Tree, tunnelUsedBy, pedestrians]
-
A.
usesTunnel
chosen
Indicates that one entity makes use of a tunnel as a passage or route to reach or connect to another entity.
-
B.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
C.
tunnelName
Indicates the name assigned to a specific tunnel in the relationship or data model.
-
D.
hasTunnel
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
E.
tunnels
Indicates that one entity passes through, under, or within another entity via a tunnel-like passage or structure.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc603220508190b64e22dec3ee5ceb |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.