Triple
T29230306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dao people |
E741047
|
entity |
| Predicate | useChineseCharactersHistorically |
P104816
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dao people, useChineseCharactersHistorically, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useChineseCharactersHistorically Context triple: [Dao people, useChineseCharactersHistorically, true]
-
A.
usedChineseCharacters
chosen
Indicates that one entity employed or wrote using Chinese characters in relation to another entity or context.
-
B.
ChineseNameTraditional
Indicates that an entity’s name is given in traditional Chinese characters.
-
C.
hasTraditionalCharacter
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
-
D.
oldChineseReconstruction
Indicates that something represents a reconstructed form or pronunciation in Old Chinese.
-
E.
containsHistoricCharacters
Indicates that something includes or features characters who are historically significant or based on real historical figures.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645d37c48190a48b3c090bfa7236 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:18 p.m.