Triple
T28808851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palmyrene temples |
E727453
|
entity |
| Predicate | underEmpire |
P38213
|
FINISHED |
| Object | Roman Empire |
—
|
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: Roman Empire | Statement: [Palmyrene temples, underEmpire, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underEmpire Context triple: [Palmyrene temples, underEmpire, Roman Empire]
-
A.
typeOfEmpire
Indicates the specific kind or classification of empire that an entity belongs to or represents.
-
B.
governingEmpire
chosen
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
C.
underTheReignOf
Indicates that one entity existed or operated during the period when another entity (typically a ruler or authority) held power or governance.
-
D.
imaginaryEmpire
Indicates a relationship where an entity rules over or belongs to an empire that exists only in imagination, fiction, or conceptual thought rather than in reality.
-
E.
associatedEmpire
Indicates a relationship where one entity is linked or connected to a particular empire, typically as belonging to, originating from, or being under the influence or control of that empire.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 6:30 a.m.