Triple
T28258491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Paz Avenue |
E712515
|
entity |
| Predicate | followsBoundaryOf |
P71578
|
FINISHED |
| Object | Autonomous City of Buenos Aires |
—
|
NE NERFINISHED |
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: Autonomous City of Buenos Aires | Statement: [General Paz Avenue, followsBoundaryOf, Autonomous City of Buenos Aires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsBoundaryOf Context triple: [General Paz Avenue, followsBoundaryOf, Autonomous City of Buenos Aires]
-
A.
isBoundaryFor
chosen
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
B.
hasBoundaryInfluenceFrom
Indicates that the boundary or limits of one entity are affected, shaped, or determined by another entity.
-
C.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
D.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
-
E.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 11:09 p.m.