Triple
T27930549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xingqing |
E707966
|
entity |
| Predicate | preModernCountry |
P153298
|
FINISHED |
| Object | China |
—
|
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: China | Statement: [Xingqing, preModernCountry, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preModernCountry Context triple: [Xingqing, preModernCountry, China]
-
A.
modernNationState
Indicates that an entity functions as a contemporary, centralized political organization with defined territory, governance, and sovereignty recognized as a nation-state.
-
B.
preModernPolityType
chosen
Indicates the classification of a polity according to its type or form of political organization in a pre-modern historical context.
-
C.
historicallyAssociatedWithModernCountry
Indicates that an entity has a significant historical connection, influence, or origin related to a specified modern country.
-
D.
preWarCountry
Indicates that a country existed or held a particular status prior to a specified war or major armed conflict.
-
E.
countryInThePast
Indicates that an entity was recognized as a country during some period in the past, but is not necessarily a country in the present.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:02 p.m.