Triple
T31835813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninshubur |
E812667
|
entity |
| Predicate | worshipEvidenceType |
P23386
|
FINISHED |
| Object | temple inscriptions |
—
|
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: temple inscriptions | Statement: [Ninshubur, worshipEvidenceType, temple inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipEvidenceType Context triple: [Ninshubur, worshipEvidenceType, temple inscriptions]
-
A.
worshipEvidence
chosen
Indicates that there is supporting information or documentation showing that one entity worships, venerates, or pays religious devotion to another.
-
B.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
C.
worshipBy
Indicates that one entity is the object of religious reverence, devotion, or adoration performed by another entity.
-
D.
worshipLinkedTo
Indicates that an act or practice of worship is connected or associated with a particular entity, concept, or context.
-
E.
worshipperType
Indicates the specific category or kind of worshipper involved in a religious or devotional relationship or action.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6aff1cb888190832f3c7785dedd1d |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:48 p.m.