Triple
T24232177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Línea 6 Circular |
E601763
|
entity |
| Predicate | isMajorTransferAxis |
P21867
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Línea 6 Circular, isMajorTransferAxis, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTransferAxis Context triple: [Línea 6 Circular, isMajorTransferAxis, true]
-
A.
isMajorAxisIn
Indicates that one entity serves as the major (longest) axis within or of another entity, such as a shape, object, or coordinate system.
-
B.
isMajorAxisFor
Indicates that something serves as the primary or longest axis that defines the main directional or structural orientation of another object or system.
-
C.
isMajorInterchangeFor
chosen
Indicates that one location functions as a primary hub where multiple routes or lines connect or transfer between each other for another location.
-
D.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
E.
isMajorFor
Indicates that one entity serves as the primary field of academic specialization (major) for another entity, typically a student.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a98a6a4819085ab955654fa444f |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.