Triple
T32797645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meroitic religion |
E838809
|
entity |
| Predicate | hasSacredStructureType |
P125205
|
FINISHED |
| Object | temple |
—
|
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 | Statement: [Meroitic religion, hasSacredStructureType, temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredStructureType Context triple: [Meroitic religion, hasSacredStructureType, temple]
-
A.
hasSacredPrecinct
Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
-
B.
hasCultPlaceType
chosen
Indicates that an entity is associated with a place used for cultic or religious activities of a specified type.
-
C.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
D.
hasPantheonStructure
Indicates that an entity possesses or is associated with a pantheon-like hierarchical structure, typically organizing multiple deities or divine figures.
-
E.
hasSacredBridge
Indicates that one entity possesses or is associated with a bridge regarded as sacred or holy in relation to another 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:14 a.m.