Triple
T8916517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekur |
E212307
|
entity |
| Predicate | statusInNippur |
P86368
|
FINISHED |
| Object | principal sanctuary |
—
|
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: principal sanctuary | Statement: [Ekur, statusInNippur, principal sanctuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInNippur Context triple: [Ekur, statusInNippur, principal sanctuary]
-
A.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
B.
statusInRevelation
Indicates the role, condition, or standing that an entity holds within the context of a particular revelation or revealed message.
-
C.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
D.
AshuraStatueStatus
Indicates the current condition or state of an Ashura statue in relation to a specified context or event.
-
E.
statusInYomi
Indicates the role, rank, or condition an entity holds within the realm or context of Yomi.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6610cd48819090a184c5f9465626 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.