Triple
T22508415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shunde District |
E556447
|
entity |
| Predicate | administrativeStatusChangedFrom |
P14579
|
FINISHED |
| Object | county |
—
|
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: county | Statement: [Shunde District, administrativeStatusChangedFrom, county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeStatusChangedFrom Context triple: [Shunde District, administrativeStatusChangedFrom, county]
-
A.
formerAdministrativeStatus
chosen
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
B.
administrativeStatusCurrent
Indicates the current administrative status or condition of an entity within a governing or managing system.
-
C.
statusChange
Indicates a transition in an entity’s state or condition from one status to another over time.
-
D.
legalStatusChangedIn
Indicates that an entity’s legal status was altered or reclassified within a specified jurisdiction, context, or time frame.
-
E.
administrativeStatusOfEntityRepresented
Indicates the current administrative or operational status assigned to the entity that is being represented.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5ebe5881908a22d519128415f2 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.