Triple
T33900669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amdang |
E869037
|
entity |
| Predicate | ethnicExonym |
P4705
|
FINISHED |
| Object | Biltine |
—
|
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: Biltine | Statement: [Amdang, ethnicExonym, Biltine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicExonym Context triple: [Amdang, ethnicExonym, Biltine]
-
A.
ethnonym
Indicates that one entity is the name of an ethnic group used to refer to the people associated with another entity.
-
B.
hasExonym
chosen
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
-
C.
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.
-
D.
equivalentEthnonym
Indicates that two different ethnonyms refer to the same ethnic group or people.
-
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.
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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 1, 2026, 1:48 a.m.