Triple
T27265459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianjin Metro Line Z16 |
E687888
|
entity |
| Predicate | hasPlannedOpening |
P175974
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [Tianjin Metro Line Z16, hasPlannedOpening, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedOpening Context triple: [Tianjin Metro Line Z16, hasPlannedOpening, unknown]
-
A.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
B.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
C.
plannedOpeningPeriod
Indicates the time span during which something is scheduled or intended to open or begin operating.
-
D.
isOpeningFor
Indicates that one entity serves as the beginning, introduction, or initial act for another entity, such as an event, performance, or sequence.
-
E.
hasOpeningCompany
Indicates that one entity is the company responsible for opening, initiating, or starting the other entity (such as an account, contract, or process).
- F. None of above. chosen
Provenance (4 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 27, 2026, 10:55 a.m.