Triple
T28332466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mosè in Egitto |
E717570
|
entity |
| Predicate | hasSacredElements |
P40534
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mosè in Egitto, hasSacredElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredElements Context triple: [Mosè in Egitto, hasSacredElements, true]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
hasRitualElements
chosen
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
-
C.
sacredElement
Indicates that one entity is regarded as holy, revered, or spiritually significant within the religious or cultural context of the other entity.
-
D.
hasSacredImage
Indicates that one entity possesses or is associated with an image regarded as sacred or religiously significant.
-
E.
hasSacredNumber
Indicates that a particular number is regarded as sacred, holy, or spiritually significant in relation to an entity.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 12:33 a.m.