Triple
T6012338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Wadi es-Sebua site |
E133864
|
entity |
| Predicate | templeStyle |
P18959
|
FINISHED |
| Object | ancient Egyptian temple architecture (relocated) |
—
|
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: ancient Egyptian temple architecture (relocated) | Statement: [New Wadi es-Sebua site, templeStyle, ancient Egyptian temple architecture (relocated)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeStyle Context triple: [New Wadi es-Sebua site, templeStyle, ancient Egyptian temple architecture (relocated)]
-
A.
templeType
chosen
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
B.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
C.
templePractice
Indicates a religious or ritual activity that is performed within or in connection with a temple.
-
D.
templeName
Indicates that an entity is identified by or associated with the name of a temple.
-
E.
templeConstruction
Indicates the action or process of building, erecting, or establishing a temple or similar sacred structure.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f5159bc8190a988293bbbb99d24 |
completed | March 22, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.