Triple
T25714353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crocodilopolis |
E644819
|
entity |
| Predicate | sacredAnimalAssociatedDeity |
P51997
|
FINISHED |
| Object | Sobek |
—
|
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: Sobek | Statement: [Crocodilopolis, sacredAnimalAssociatedDeity, Sobek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredAnimalAssociatedDeity Context triple: [Crocodilopolis, sacredAnimalAssociatedDeity, Sobek]
-
A.
hasAnimalDeity
Indicates that an entity recognizes, worships, or is associated with a deity represented in animal form.
-
B.
veneratedAnimal
Indicates that an animal is regarded with deep respect, reverence, or sacred status by someone or within a culture.
-
C.
patronDeityOf
chosen
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).
-
D.
attributeOfDeity
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
E.
worshippedDeityCulture
Indicates that a particular culture reveres, honors, or practices religious devotion toward a specific deity.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc610aac81909ee4722dcfcca67d |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 9:37 p.m.