Triple
T21941652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monumental Axis bus corridor |
E541836
|
entity |
| Predicate | isKeySpineFor |
P146631
|
FINISHED |
| Object | urban mobility in Brasília |
—
|
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: urban mobility in Brasília | Statement: [Monumental Axis bus corridor, isKeySpineFor, urban mobility in Brasília]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeySpineFor Context triple: [Monumental Axis bus corridor, isKeySpineFor, urban mobility in Brasília]
-
A.
isKeyBodyOf
Indicates that one entity serves as the primary or central body/content component of another entity.
-
B.
isKeyPostIn
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
-
C.
hasSpines
Indicates that one entity possesses or is characterized by spines or spine-like structures.
-
D.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
E.
areKeyTo
Indicates that something is essential or critically important for enabling, achieving, or understanding something else.
- F. None of above. chosen
Provenance (4 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12422245c8190af128b29e2d9c1fc |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb6991948190a428c3c3bfd1c3b8 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:56 p.m.