Triple
T7300599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 89 |
E167838
|
entity |
| Predicate | hasServiceAreaType |
P68386
|
FINISHED |
| Object | rest areas |
—
|
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: rest areas | Statement: [Interstate 89, hasServiceAreaType, rest areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceAreaType Context triple: [Interstate 89, hasServiceAreaType, rest areas]
-
A.
hasServiceAreas
Indicates that an entity provides services within, or is operational across, specific geographic or functional areas.
-
B.
areaServedType
chosen
Indicates the type or category of area that is served by an entity or service.
-
C.
hasPrimaryServiceArea
Indicates that an entity is associated with a main geographic or functional area in which it primarily provides its services.
-
D.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
E.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebaef4a081908fadc6d5e2621e80 |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.