Triple
T28599189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buenos Aires Underground |
E723858
|
entity |
| Predicate | firstLineTerminus |
P46766
|
FINISHED |
| Object | Plaza de Mayo |
—
|
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: Plaza de Mayo | Statement: [Buenos Aires Underground, firstLineTerminus, Plaza de Mayo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLineTerminus Context triple: [Buenos Aires Underground, firstLineTerminus, Plaza de Mayo]
-
A.
lineTerminusForSomeServices
Indicates that a location serves as the endpoint or terminus for at least some, but not necessarily all, of the services operating on a given line.
-
B.
lineTerminusFor
chosen
Indicates that one entity serves as an endpoint or terminus of a particular line or linear feature represented by another entity.
-
C.
definesLineTerminator
Indicates that one entity specifies what character or sequence of characters marks the end of a line for another entity.
-
D.
lineTerminusDirection
Indicates the directional orientation or bearing at which a line segment or route terminates at its endpoint.
-
E.
finalLine
Indicates that something is the last or concluding line in a sequence, text, or structured content.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
Created at: April 28, 2026, 4:23 a.m.