Triple
T10345550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Federal Highway 85 |
E243734
|
entity |
| Predicate | hasFreeSections |
P72697
|
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: [Mexican Federal Highway 85, hasFreeSections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFreeSections Context triple: [Mexican Federal Highway 85, hasFreeSections, yes]
-
A.
hasFreeZone
Indicates that an entity includes or is associated with a designated free zone area where special rules, privileges, or exemptions apply.
-
B.
hasFreeEntry
Indicates that access to something (such as an event, place, or service) does not require payment of an entry fee.
-
C.
hasNonFreeRepositorySection
Indicates that an entity includes a section or component that is classified as non-free (e.g., proprietary or restricted) within its repository.
-
D.
hasFreeRoads
chosen
Indicates that an entity provides or is associated with roads that can be used without paying tolls or fees.
-
E.
freeSection
Indicates that a section or segment is available without cost or restrictions to the user.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e923e3d08190971073ce41ff860f |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:56 a.m.