Triple
T33085289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sety I |
E846621
|
entity |
| Predicate | majorTempleProject |
P8490
|
FINISHED |
| Object | Temple of Sety I at Abydos |
—
|
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: Temple of Sety I at Abydos | Statement: [Sety I, majorTempleProject, Temple of Sety I at Abydos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTempleProject Context triple: [Sety I, majorTempleProject, Temple of Sety I at Abydos]
-
A.
templeConstruction
Indicates the action or process of building, erecting, or establishing a temple or similar sacred structure.
-
B.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
C.
mainTemple
chosen
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
majorTempleManagingBody
Indicates that an entity serves as the primary governing or administrative body responsible for managing a major temple.
-
E.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: May 1, 2026, 1:26 a.m.