Triple
T12037279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appius Claudius Pulcher |
E286572
|
entity |
| Predicate | heldImperium |
P32437
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Appius Claudius Pulcher, heldImperium, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldImperium Context triple: [Appius Claudius Pulcher, heldImperium, yes]
-
A.
heldImperialImmediacy
Indicates that an entity possessed imperial immediacy, meaning it was directly subject to the authority of the emperor rather than to any intermediate feudal lord.
-
B.
couldHoldImperium
chosen
Indicates that one entity had the legal or formal capacity to exercise supreme authoritative power or command over another or within a given domain.
-
C.
heldInEmpire
Indicates that an event, position, or status occurred or existed within the territorial or political bounds of a particular empire.
-
D.
wasHegemonOf
Indicates that one entity held dominant political, military, or economic leadership over another entity or group.
-
E.
heldImperialEstate
Indicates that an entity possessed or controlled land or property classified as an imperial estate under a particular imperial authority.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.