Triple
T6648014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilean national road network |
E150749
|
entity |
| Predicate | hasKeyAxis |
P43001
|
FINISHED |
| Object | north–south longitudinal axis |
—
|
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: north–south longitudinal axis | Statement: [Chilean national road network, hasKeyAxis, north–south longitudinal axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyAxis Context triple: [Chilean national road network, hasKeyAxis, north–south longitudinal axis]
-
A.
hasAxisConfiguration
chosen
Indicates that one entity specifies or defines the axis arrangement, orientation, or setup used by another entity.
-
B.
hasKeyState
Indicates that an entity possesses or is associated with a particular key-related status or condition (such as pressed, released, enabled, or disabled).
-
C.
hasKeyMovement
Indicates that one entity possesses or defines the primary or characteristic movement pattern associated with another entity.
-
D.
hasKeyEvent
Indicates that an entity includes, is associated with, or is characterized by a significant or defining event.
-
E.
hasKeyAction
Indicates that an entity performs or is associated with a primary or essential action within a given context.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2 p.m.