Triple
T23709338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | República (São Paulo Metro) station |
E585815
|
entity |
| Predicate | line3SectionOpening |
P42368
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [República (São Paulo Metro) station, line3SectionOpening, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: line3SectionOpening Context triple: [República (São Paulo Metro) station, line3SectionOpening, 1979]
-
A.
line3OpeningSegment
Indicates that something is the initial or opening segment of a third line in a sequence or structure.
-
B.
lineSectionOpenedWith
Indicates that a specific section of a line (such as a route, track, or service line) has been officially opened or put into operation by a particular action or event.
-
C.
line1Section
Indicates that one entity is a specific section or segment of another entity referred to as "line1."
-
D.
line9OpeningSection
Indicates that something occurs in or pertains to the opening section of line 9.
-
E.
line3OpeningDate
chosen
Indicates the calendar date on which the third line (e.g., a route, service line, or similar system component) was officially opened or began operation.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b775a4288190bbee7bd4b5bbcd75 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.