Triple
T22441801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chengdu Metro Line 1 |
E554769
|
entity |
| Predicate | firstPhaseOpeningDate |
P51679
|
FINISHED |
| Object | 2010-09-27 |
—
|
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: 2010-09-27 | Statement: [Chengdu Metro Line 1, firstPhaseOpeningDate, 2010-09-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPhaseOpeningDate Context triple: [Chengdu Metro Line 1, firstPhaseOpeningDate, 2010-09-27]
-
A.
phase1OpeningDate
chosen
Indicates the date on which the first phase of a project, development, or initiative is officially opened or begins operation.
-
B.
firstLineOpeningDate
Indicates the date on which the first line in a system, network, or service was officially opened or began operation.
-
C.
firstPhaseEndDate
Indicates the date on which the first phase of a process, project, or activity is completed or scheduled to end.
-
D.
firstPhaseStart
Indicates the point in time when the initial phase of a process or sequence begins.
-
E.
softOpeningDate
Indicates the date on which a business, venue, or service begins limited or trial operations before its official grand opening.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae2f7608190b1c1e8bd12ca2162 |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.