Triple
T29645367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamberlain’s Ranch |
E755983
|
entity |
| Predicate | startingDirection |
P160897
|
FINISHED |
| Object | top‑down Narrows route |
—
|
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: top‑down Narrows route | Statement: [Chamberlain’s Ranch, startingDirection, top‑down Narrows route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingDirection Context triple: [Chamberlain’s Ranch, startingDirection, top‑down Narrows route]
-
A.
directionFromStart
chosen
Indicates the orientation or path taken moving outward from a defined starting point toward another location or object.
-
B.
departureDirection
Indicates the direction or bearing in which an entity moves away from its point of origin or starting location.
-
C.
startingForwardEast
Indicates that an entity begins its movement or orientation facing toward the east direction.
-
D.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
E.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: April 28, 2026, 6:49 p.m.