Triple
T35587109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 연산역 |
E1028387
|
entity |
| Predicate | 3LineServiceStartDate |
P42368
|
FINISHED |
| Object | 2005-11-28 |
—
|
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: 2005-11-28 | Statement: [연산역, 3LineServiceStartDate, 2005-11-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 3LineServiceStartDate Context triple: [연산역, 3LineServiceStartDate, 2005-11-28]
-
A.
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.
-
B.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
C.
serviceEntryDate
Indicates the date on which a service or duty officially began or was first entered into the record.
-
D.
blueLineServiceBegan
Indicates that service on the Blue Line began operating at a specified time or event.
-
E.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.