Triple
T30047440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dae Joyeong |
E763492
|
entity |
| Predicate | possibleEthnicity |
P120284
|
FINISHED |
| Object | Mohe people |
—
|
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: Mohe people | Statement: [Dae Joyeong, possibleEthnicity, Mohe people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleEthnicity Context triple: [Dae Joyeong, possibleEthnicity, Mohe people]
-
A.
likelyNationalOrigin
Indicates that one entity is inferred or predicted to have a particular national origin based on available information or context.
-
B.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
C.
mayBelongToEthnicGroup
chosen
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
D.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
-
E.
hasEthnicScope
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 6:54 p.m.