Triple
T35050384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Falls |
E1011312
|
entity |
| Predicate | approximateRoundTripDistanceFromAdirondakLoj |
P199511
|
FINISHED |
| Object | about 7 miles |
—
|
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 7 miles | Statement: [Indian Falls, approximateRoundTripDistanceFromAdirondakLoj, about 7 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateRoundTripDistanceFromAdirondakLoj Context triple: [Indian Falls, approximateRoundTripDistanceFromAdirondakLoj, about 7 miles]
-
A.
approximateRoundTripDistanceFromTrailhead
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
B.
hasApproximateRoundTripDistanceFromMaroonLake
Indicates that an entity has an approximate total round-trip distance measured from Maroon Lake.
-
C.
distanceToPoughkeepsie
Indicates the spatial distance between a given entity and the location of Poughkeepsie.
-
D.
distanceToRochesterNY
Indicates the spatial distance between a given entity’s location and the location of Rochester, New York.
-
E.
distanceFromOlean (miles)
Indicates the number of miles separating a given location from Olean.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
| PDg | Predicate description generation | batch_69ff3fb151008190bf8a90f9f1c5f0c8 |
completed | May 9, 2026, 2:07 p.m. |
Created at: May 3, 2026, 4:01 p.m.