Triple
T30924561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kwoth |
E787820
|
entity |
| Predicate | hasConceptVariant |
P455
|
FINISHED |
| Object | Kwoth nhial (God of the sky) |
E394044
|
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: Kwoth nhial (God of the sky) | Statement: [Kwoth, hasConceptVariant, Kwoth nhial (God of the sky)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConceptVariant Context triple: [Kwoth, hasConceptVariant, Kwoth nhial (God of the sky)]
-
A.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
B.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
C.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
D.
hasVariantSystem
Indicates that one system is an alternative or variant form of another system within the same general framework or category.
-
E.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
- F. None of above.
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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01a9e333fc819087d583ff319be0b3 |
completed | May 11, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28e46b4f4c81908eb3788972bbde88 |
completed | June 10, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_6a01a877c9e08190b0678618d3533286 |
completed | May 11, 2026, 9:59 a.m. |
Created at: April 29, 2026, 8:51 p.m.