Triple
T8615414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Scenic Byway |
E204022
|
entity |
| Predicate | appliesToTypeOfResource |
P3729
|
FINISHED |
| Object | transportation corridor |
—
|
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: transportation corridor | Statement: [New York State Scenic Byway, appliesToTypeOfResource, transportation corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToTypeOfResource Context triple: [New York State Scenic Byway, appliesToTypeOfResource, transportation corridor]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
hasTypeOfResource
chosen
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
C.
isResourceFor
Indicates that one entity serves as a resource, support, or means of use for another entity.
-
D.
appliesToPropertyType
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
E.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc47020748819090f658c115c1a7b9 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.