Triple
T34537327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khmun |
E886704
|
entity |
| Predicate | sacredAnimalAssociated |
P146240
|
FINISHED |
| Object | ibis |
—
|
LITERAL 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: ibis | Statement: [Khmun, sacredAnimalAssociated, ibis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredAnimalAssociated Context triple: [Khmun, sacredAnimalAssociated, ibis]
-
A.
veneratedAnimal
chosen
Indicates that an animal is regarded with deep respect, reverence, or sacred status by someone or within a culture.
-
B.
hasAnimalDeity
Indicates that an entity recognizes, worships, or is associated with a deity represented in animal form.
-
C.
animalSymbol
Indicates that one entity serves as a symbolic representation or emblem of the other in the form of an animal.
-
D.
patronDeityOf
Indicates that one entity serves as the protective or primary deity associated with, worshipped by, or presiding over another entity (such as a person, group, or place).
-
E.
closelyAssociatedDeity
Indicates a deity that is strongly connected or frequently linked to another entity, such as a person, place, object, or concept, through special association or significance.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71feeedc081908468bf1e2e2ef3e0 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.