Triple
T30976891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seti I |
E789254
|
entity |
| Predicate | templeProject |
P67282
|
FINISHED |
| Object | Great Hypostyle Hall at Karnak |
—
|
NE NERFINISHED |
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: Great Hypostyle Hall at Karnak | Statement: [Seti I, templeProject, Great Hypostyle Hall at Karnak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: templeProject Context triple: [Seti I, templeProject, Great Hypostyle Hall at Karnak]
-
A.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
-
B.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
C.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
D.
templeUse
Indicates that something is used as, functions as, or serves the purpose of a temple.
-
E.
templeConstruction
chosen
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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.