Triple
T29815220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese civilization |
E757084
|
entity |
| Predicate | hasCoreEthnicGroup |
P181074
|
FINISHED |
| Object | Han Chinese |
—
|
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: Han Chinese | Statement: [Chinese civilization, hasCoreEthnicGroup, Han Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreEthnicGroup Context triple: [Chinese civilization, hasCoreEthnicGroup, Han Chinese]
-
A.
hasEthnicCore
chosen
Indicates that an entity possesses a central or defining ethnic group that forms the core of its identity or composition.
-
B.
hasRecognizedEthnicGroup
Indicates that an entity includes or is associated with an ethnic group that is officially or socially recognized as distinct.
-
C.
hasEthnicGroupType
Indicates that an entity is associated with, characterized by, or classified according to a particular type or category of ethnic group.
-
D.
isUsedByEthnicGroup
Indicates that something (such as an object, practice, or resource) is utilized or employed by a particular ethnic group.
-
E.
containedEthnicGroup
Indicates that one entity (typically a larger group, region, or population) includes or encompasses a particular ethnic group within it.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00ac5654a0819090701f61a5802d64 |
completed | May 10, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_6a00ab94b5e881909e15d1342e5f43be |
completed | May 10, 2026, 4 p.m. |
Created at: April 29, 2026, 5:26 p.m.