Triple
T30162167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lex Manilia |
E766696
|
entity |
| Predicate | grantedImperium |
P97735
|
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, grantedImperium, Pompey the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedImperium Context triple: [Lex Manilia, grantedImperium, Pompey the Great]
-
A.
grantedToEmperor
Indicates that something (such as a right, title, privilege, or possession) has been formally given or conferred to an emperor.
-
B.
grantedImperialImmediacyBy
Indicates that an entity received the special legal-political status of imperial immediacy directly from a specified imperial authority.
-
C.
grantedIn
Indicates that something (such as a right, status, or permission) is formally conferred or authorized within a particular context, document, or jurisdiction.
-
D.
grantedAs
chosen
Indicates that one entity is conferred, assigned, or bestowed in a particular role, status, or capacity to another entity.
-
E.
grantedHonor
Indicates that one entity has formally bestowed an honor, award, or distinction upon another entity.
- 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_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 7:22 p.m.