Triple
T3477442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treman Triangle |
E73407
|
entity |
| Predicate | trailTypeAccessed |
P2401
|
FINISHED |
| Object | gorge trail |
—
|
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: gorge trail | Statement: [Treman Triangle, trailTypeAccessed, gorge trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailTypeAccessed Context triple: [Treman Triangle, trailTypeAccessed, gorge trail]
-
A.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
B.
trailAssociation
Indicates an associative relationship between entities where one is contextually or functionally linked to a trail (such as being located on, connected to, or part of that trail).
-
C.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
-
D.
hasTrailType
chosen
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
E.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb5b7584819096eadd1c5268eab1 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae07802c8190919c49b0e65b2797 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.