Triple
T30221128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | censor (Roman Republic) |
E768346
|
entity |
| Predicate | hadImperium |
P32437
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [censor (Roman Republic), hadImperium, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadImperium Context triple: [censor (Roman Republic), hadImperium, no]
-
A.
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.
-
B.
wasHegemonOf
Indicates that one entity held dominant political, military, or economic leadership over another entity or group.
-
C.
hadImperialCircle
Indicates that an entity was administratively organized within a specific Imperial Circle of the Holy Roman Empire.
-
D.
hadTyrant
Indicates that an entity was ruled or dominated by a tyrant.
-
E.
hadImperialStatus
Indicates that an entity possessed or was granted imperial rank, authority, or official status within an 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6801da3e88190a4862f59160e6832 |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:35 p.m.