Triple
T10730661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Geun-hye |
E253062
|
entity |
| Predicate | removalDecisionDate |
P49888
|
FINISHED |
| Object | 2017-03-10 |
—
|
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: 2017-03-10 | Statement: [Park Geun-hye, removalDecisionDate, 2017-03-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removalDecisionDate Context triple: [Park Geun-hye, removalDecisionDate, 2017-03-10]
-
A.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
-
B.
deJureRemovalDate
chosen
Indicates the official, legally recognized date on which an entity is formally removed from a position, status, or record.
-
C.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
-
D.
damRemovalCompletionDate
Indicates the date on which the removal of a dam is fully completed.
-
E.
removalPeriod
Indicates the time span during which something is taken away, deleted, or otherwise removed from availability or consideration.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70fcb1cd881909635def59ad5d19c |
completed | April 9, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.