Triple
T30162166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lex Manilia |
E766696
|
entity |
| Predicate | extendedImperiumOf |
P38213
|
FINISHED |
| Object | Pompey the Great |
—
|
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: Pompey the Great | Statement: [Lex Manilia, extendedImperiumOf, Pompey the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedImperiumOf Context triple: [Lex Manilia, extendedImperiumOf, Pompey the Great]
-
A.
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.
-
B.
governingEmpire
chosen
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
C.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
D.
imperialAdministration
Indicates the exercise or structure of centralized governing authority by an empire over its territories or subjects.
-
E.
historicalEmpireCenter
Indicates that a location served as the primary political or administrative center of a historical 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67edb30d8819097a9f90443428fc2 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:22 p.m.