Triple
T20910498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provincial Route 25 (Chubut) |
E514927
|
entity |
| Predicate | terminusARegion |
P36184
|
FINISHED |
| Object | Atlantic coast of Chubut |
—
|
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: Atlantic coast of Chubut | Statement: [Provincial Route 25 (Chubut), terminusARegion, Atlantic coast of Chubut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusARegion Context triple: [Provincial Route 25 (Chubut), terminusARegion, Atlantic coast of Chubut]
-
A.
terminusRegion
chosen
Indicates the region or area where something (such as a route, line, or process) ends or reaches its final point.
-
B.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
C.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
D.
terminusInland
Indicates that something ends, concludes, or has its final point within an inland area rather than at a coast or shoreline.
-
E.
terminusAdjacentTo
Indicates that one terminus (end point) of a route, line, or feature is directly next to or immediately bordering another terminus.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec5e3f988190932956119197e3b1 |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.