Triple
T38662325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiwanese people |
E940365
|
entity |
| Predicate | homeCountryPoliticalStatus |
P71945
|
FINISHED |
| Object | de facto independent state |
—
|
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: de facto independent state | Statement: [Taiwanese people, homeCountryPoliticalStatus, de facto independent state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeCountryPoliticalStatus Context triple: [Taiwanese people, homeCountryPoliticalStatus, de facto independent state]
-
A.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
-
B.
countryOfCitizenship
Indicates the country in which a person or entity holds legal citizenship.
-
C.
isPoliticalStatus
chosen
Indicates that a relationship specifies the political condition, classification, or standing associated with an entity.
-
D.
stateOfCitizenship
Indicates the legal nationality or country to which a person formally belongs as a citizen.
-
E.
homeCountryGovernment
Indicates that a government is the official governing authority of the country that is the home or origin state of the referenced 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:33 p.m.