Triple
T33816270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 67 (Arizona) |
E866685
|
entity |
| Predicate | restrictedBySeason |
P177844
|
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: [State Route 67 (Arizona), restrictedBySeason, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restrictedBySeason Context triple: [State Route 67 (Arizona), restrictedBySeason, yes]
-
A.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
B.
requiresSameSeason
Indicates that the related entities must occur, be available, or be used within the same season.
-
C.
visibleInSeason
Indicates that something can be seen or is observable during a particular season.
-
D.
isSeasonalRelease
Indicates that something is released only during a specific season or limited time period tied to the calendar.
-
E.
requiresPermitDuringSeason
Indicates that performing an activity or accessing a resource during a specified season is conditional on obtaining a permit.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f70519f114819080659840c04d7911 |
completed | May 3, 2026, 8:19 a.m. |
Created at: May 1, 2026, 1:46 a.m.