Triple
T28790922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huang Wei-che |
E726948
|
entity |
| Predicate | locatedInTheCountryGoverned |
P200816
|
FINISHED |
| Object | Taiwan |
—
|
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: Taiwan | Statement: [Huang Wei-che, locatedInTheCountryGoverned, Taiwan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTheCountryGoverned Context triple: [Huang Wei-che, locatedInTheCountryGoverned, Taiwan]
-
A.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
B.
locatedInTheCountryOfOffice
Indicates that an office or organizational branch is situated within the specified country.
-
C.
locatedInSubnationalEntity
Indicates that one entity is geographically or administratively situated within a specific subnational division, such as a state, province, or region.
-
D.
locatedOnTerritoryOf
Indicates that one entity is situated within or on the land area governed or owned by another entity.
-
E.
locatedInCapital
Indicates that an entity is situated within the capital city of a specified region, country, or administrative area.
- F. None of above. chosen
Provenance (4 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_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69ffb120b9988190b6361c69265033c0 |
completed | May 9, 2026, 10:11 p.m. |
Created at: April 28, 2026, 6:23 a.m.