Triple
T12156331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Hathor |
E289582
|
entity |
| Predicate | modifiedDuringReignOf |
P103248
|
FINISHED |
| Object | Roman emperors |
—
|
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: Roman emperors | Statement: [Temple of Hathor, modifiedDuringReignOf, Roman emperors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiedDuringReignOf Context triple: [Temple of Hathor, modifiedDuringReignOf, Roman emperors]
-
A.
builtDuringReignOf
Indicates that something was constructed while a particular ruler or authority was in power.
-
B.
functionDuringReign
Indicates that a function, role, or activity occurred or was performed during the time span of a particular ruler’s reign.
-
C.
ruledDuringReignOf
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
-
D.
activeInReignOf
Indicates that an entity was active or operational during the time period corresponding to a specific ruler’s reign.
-
E.
adoptedDuringReignOf
Indicates that one entity (such as a law, policy, or practice) was adopted or came into effect while another entity (typically a ruler or leader) was in power or reigning.
- F. None of above. chosen
Provenance (4 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d915d58ab881908b5b7901990308a4 |
completed | April 10, 2026, 3:23 p.m. |
Created at: April 8, 2026, 9:50 p.m.