Triple
T38294450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunder Dragon |
E1022452
|
entity |
| Predicate | hasNameInDzongkha |
P201208
|
FINISHED |
| Object | Druk |
—
|
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: Druk | Statement: [Thunder Dragon, hasNameInDzongkha, Druk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInDzongkha Context triple: [Thunder Dragon, hasNameInDzongkha, Druk]
-
A.
nameInTibetan
Indicates that an entity’s name is expressed or written in the Tibetan language.
-
B.
hasOfficialNameInNepali
Indicates that an entity has an official name expressed in the Nepali language.
-
C.
hasNameInMongolian
Indicates that an entity is associated with a specific name expressed in the Mongolian language.
-
D.
hasNameInHmong
Indicates that an entity is associated with a specific name expressed in the Hmong language.
-
E.
hasNameInAymaraOrQuechua
Indicates that an entity is known by a specific name expressed in either the Aymara or Quechua language.
- F. None of above. chosen
Provenance (4 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
| PDg | Predicate description generation | batch_69ffde916fcc81908d6e1b4e6d3f761c |
completed | May 10, 2026, 1:25 a.m. |
Created at: May 3, 2026, 4:30 p.m.