Triple
T16892141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Precinct of Mut |
E424199
|
entity |
| Predicate | hasSacredAnimalAssociation |
P75085
|
FINISHED |
| Object | lioness |
—
|
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: lioness | Statement: [Precinct of Mut, hasSacredAnimalAssociation, lioness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredAnimalAssociation Context triple: [Precinct of Mut, hasSacredAnimalAssociation, lioness]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
hasAnimalCult
chosen
Indicates that an entity practices or maintains a cult or organized religious veneration centered around one or more animals.
-
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.
hasMythologicalBearer
Indicates that something is associated with, carried by, or represented by a figure from mythology.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc5a5308190937ebd05356bd91d |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.