Triple
T23661126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dachen Islands |
E584447
|
entity |
| Predicate | formerInhabitantsRelocatedTo |
P1660
|
FINISHED |
| Object | Taiwan |
E141325
|
NE 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: Taiwan | Statement: [Dachen Islands, formerInhabitantsRelocatedTo, Taiwan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerInhabitantsRelocatedTo Context triple: [Dachen Islands, formerInhabitantsRelocatedTo, Taiwan]
-
A.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
-
B.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
C.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
D.
formerResidenceOf
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
-
E.
influencedRelocationOf
Indicates that one entity played a causal or motivating role in another entity’s decision or action to move from one location to another.
- F. None of above.
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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b3601ce481909a4ae9d633b9a343 |
completed | April 29, 2026, 7:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0f4543c3bc819088d200fd3db69512 |
completed | May 21, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.