Triple
T1526467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 75 near Lake City |
E32345
|
entity |
| Predicate | hasRestAreas |
P29828
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Interstate 75 near Lake City, hasRestAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestAreas Context triple: [Interstate 75 near Lake City, hasRestAreas, yes]
-
A.
hasRestrooms
Indicates that a place or facility provides access to restroom or toilet amenities.
-
B.
hasRecreationalArea
Indicates that an entity includes, provides, or is associated with a designated space intended for leisure or recreational activities.
-
C.
hasRecreationalRoute
Indicates that an entity is associated with or includes a route intended for recreational activities such as walking, cycling, or hiking.
-
D.
hasCampground
Indicates that one entity provides, contains, or is associated with a campground facility or area for another entity.
-
E.
hasDropOffArea
Indicates that an entity provides a designated area where items, passengers, or goods can be temporarily left or unloaded.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a933ddc5a881909cdf503f2bc29bd4 |
completed | March 5, 2026, 7:42 a.m. |
| PD | Predicate disambiguation | batch_69a907ae8f688190ad9000ea1e018585 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a933dce3488190b20f0e3d37d16371 |
completed | March 5, 2026, 7:42 a.m. |
Created at: March 4, 2026, 7:26 p.m.