Triple
T14890023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universidad de Chile metro station |
E359729
|
entity |
| Predicate | openingDateLine3Platforms |
P42368
|
FINISHED |
| Object | 2019-01-22 |
—
|
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: 2019-01-22 | Statement: [Universidad de Chile metro station, openingDateLine3Platforms, 2019-01-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateLine3Platforms Context triple: [Universidad de Chile metro station, openingDateLine3Platforms, 2019-01-22]
-
A.
openingDateLine8Platforms
Indicates the date on which the Line 8 platforms were officially opened for use.
-
B.
openingDateOnLine
Indicates the date on which a particular service, facility, or segment first began operating on a specified line.
-
C.
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.
-
D.
line9PlatformsOpeningDate
Indicates the date on which the platforms for line 9 were first opened for use.
-
E.
openingDateLine16
Indicates the date on which line 16 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f6cf5c8190b6b28f58fafe5d59 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 2:09 a.m.