Triple
T16299728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linkou District |
E395751
|
entity |
| Predicate | upgradeEffectiveDate |
P23059
|
FINISHED |
| Object | 2010-12-25 |
—
|
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-12-25 | Statement: [Linkou District, upgradeEffectiveDate, 2010-12-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradeEffectiveDate Context triple: [Linkou District, upgradeEffectiveDate, 2010-12-25]
-
A.
upgradeDate
chosen
Indicates the date on which an entity was upgraded to a newer or improved version.
-
B.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
C.
upgradePeriod
Indicates the time span or interval during which an upgrade is valid, active, or can be performed.
-
D.
currentVersionEffectiveDate
Indicates the date from which the current version of an item, record, or agreement becomes valid and in effect.
-
E.
updatedSpecificationDate
Indicates the date on which a specification was last revised or brought up to date.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e31c9e8819094593f3aeb44f2ca |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.