Triple
T31596881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yanjin County |
E806240
|
entity |
| Predicate | upperAdministrativeUnit |
P164899
|
FINISHED |
| Object | Xinxiang City |
—
|
NE NERFINISHED |
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: Xinxiang City | Statement: [Yanjin County, upperAdministrativeUnit, Xinxiang City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperAdministrativeUnit Context triple: [Yanjin County, upperAdministrativeUnit, Xinxiang City]
-
A.
administrativeUnitLevel
Indicates the hierarchical level or rank of an administrative unit within an overall administrative or governmental structure.
-
B.
isSeniorAdministrativeUnit
chosen
Indicates that one administrative unit holds a higher-level or superior administrative status relative to another unit.
-
C.
governmentalUnit
Indicates that one entity functions as a governmental or administrative unit in relation to another entity.
-
D.
laterAdministrativeUnit
Indicates that one administrative unit succeeds or replaces another in time, coming into effect at a later date.
-
E.
hasAdministrativeUnit
Indicates that one entity possesses, contains, or is associated with another entity that functions as its administrative subdivision or governing unit.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8351f14819084cc7cb548cb6645 |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:31 p.m.