Triple
T32582272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bo-Yin Yang |
E832820
|
entity |
| Predicate | primaryPlaceOfWork |
P1527
|
FINISHED |
| Object | Taipei, Taiwan |
E14412
|
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: Taipei, Taiwan | Statement: [Bo-Yin Yang, primaryPlaceOfWork, Taipei, Taiwan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPlaceOfWork Context triple: [Bo-Yin Yang, primaryPlaceOfWork, Taipei, Taiwan]
-
A.
primaryWork
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
-
B.
locationOfWork
chosen
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
C.
workedPrimarilyIn
Indicates that an entity carried out the majority of its work, activity, or career within a particular field, location, or context.
-
D.
placeOfOriginOfWork
Indicates the location where a work (such as an artwork, literary piece, or other creation) was originally produced or created.
-
E.
placeInWork
Indicates that one entity is located or occurs within the spatial or structural context of another entity in a work.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347ba6e2508190a16d03fb51adc8d1 |
completed | June 18, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:04 a.m.