Triple
T9155208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFWD |
E219690
|
entity |
| Predicate | notableTargetGroup |
P10541
|
FINISHED |
| Object | overseas Chinese diaspora |
—
|
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: overseas Chinese diaspora | Statement: [UFWD, notableTargetGroup, overseas Chinese diaspora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTargetGroup Context triple: [UFWD, notableTargetGroup, overseas Chinese diaspora]
-
A.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
-
B.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
C.
targetsGroup
chosen
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
D.
notableSubgroup
Indicates that one group forms a particularly significant or noteworthy subset within a larger group.
-
E.
notableManager
Indicates that an entity has, or is associated with, a manager who is particularly prominent, distinguished, or widely recognized.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca9d274bc8190b734a814e253d18a |
completed | April 1, 2026, 5:14 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.