Triple
T37865677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ndeʼ |
E944462
|
entity |
| Predicate | relatedEthnonyms |
P204434
|
FINISHED |
| Object | Ndee |
E1996156
|
NE 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: Ndee | Statement: [Ndeʼ, relatedEthnonyms, Ndee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEthnonyms Context triple: [Ndeʼ, relatedEthnonyms, Ndee]
-
A.
opponentEthnonyms
Indicates that one party refers to another party using ethnonyms that mark them as an opponent or adversarial group.
-
B.
relatedEthnonymLanguageContext
Indicates that an ethnonym is associated with or derived from a particular language or linguistic context.
-
C.
relatedEthnonymNote
Indicates that there is an explanatory note describing how this ethnonym is related to another ethnonym or term.
-
D.
ethnonymAttestedIn
Indicates that the name of an ethnic group (ethnonym) is documented or recorded in a specified source, context, or medium.
-
E.
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.
- F. None of above. chosen
Provenance (5 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410422d2808190b97cc5270f4aa09d |
completed | June 28, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:19 p.m.