Triple
T7881374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Island Park, Idaho |
E182985
|
entity |
| Predicate | hasLengthOfMainStreet |
P53813
|
FINISHED |
| Object | about 33 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 33 miles | Statement: [Island Park, Idaho, hasLengthOfMainStreet, about 33 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLengthOfMainStreet Context triple: [Island Park, Idaho, hasLengthOfMainStreet, about 33 miles]
-
A.
hasMainStreet
Indicates that a place or locality possesses a primary street commonly recognized as its main thoroughfare.
-
B.
hasMainResidentialStreet
Indicates that an entity is associated with or served by a specific primary street used predominantly for residential purposes.
-
C.
mainStraightLengthM
Indicates the length, measured in meters, of the main straight segment (typically of a track, road, or similar linear feature).
-
D.
hasMainStraightLengthKm
Indicates the length in kilometers of the primary or main straight segment associated with an entity.
-
E.
roadLength
chosen
Indicates the measured distance or extent of a road, typically expressed in units of length.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39c14a188190a225ca3c7e515b0c |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:58 p.m.