Triple
T28634608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khitan people |
E724740
|
entity |
| Predicate | ethnonymLegacy |
P126678
|
FINISHED |
| Object | Cathay |
—
|
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: Cathay | Statement: [Khitan people, ethnonymLegacy, Cathay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnonymLegacy Context triple: [Khitan people, ethnonymLegacy, Cathay]
-
A.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
B.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
C.
ethnonymRoot
Indicates that one term serves as the morphological or etymological root from which an ethnonym (a name for an ethnic group or people) is derived.
-
D.
ethnonymPreservedIn
chosen
Indicates that the name of an ethnic group is preserved or reflected within another term, such as a place name, personal name, or linguistic form.
-
E.
ethnonymInLanguage
Indicates that a given term is the name used in a specified language to refer to the people of a particular ethnic group or nationality.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:39 a.m.