Triple
T28790849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanli District |
E726946
|
entity |
| Predicate | changedAdministrativeStatusOn |
P35872
|
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: [Wanli District, changedAdministrativeStatusOn, 2010-12-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedAdministrativeStatusOn Context triple: [Wanli District, changedAdministrativeStatusOn, 2010-12-25]
-
A.
formerAdministrativeStatus
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
B.
statusChange
chosen
Indicates a transition in an entity’s state or condition from one status to another over time.
-
C.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
D.
legalStatusChangedIn
Indicates that an entity’s legal status was altered or reclassified within a specified jurisdiction, context, or time frame.
-
E.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:23 a.m.