Triple
T8442508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canaanite religion |
E199581
|
entity |
| Predicate | hasTempleArchitectureFeature |
P6684
|
FINISHED |
| Object | courtyard altar |
—
|
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: courtyard altar | Statement: [Canaanite religion, hasTempleArchitectureFeature, courtyard altar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempleArchitectureFeature Context triple: [Canaanite religion, hasTempleArchitectureFeature, courtyard altar]
-
A.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
B.
hasTemplePurpose
Indicates that something (such as a building, site, or structure) is intended, used, or designated for temple-related purposes or functions.
-
C.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
D.
hasRockCutTempleComplex
Indicates that an entity possesses or contains a complex of temples that have been carved directly into rock formations.
-
E.
hasTempleCount
Indicates that an entity is associated with a specified number of temples.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe310d8e08190b871bda79acde678 |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.