Triple
T5796096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curiate Assembly |
E128511
|
entity |
| Predicate | conferred |
P18219
|
FINISHED |
| Object | imperium on magistrates |
—
|
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: imperium on magistrates | Statement: [Curiate Assembly, conferred, imperium on magistrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferred Context triple: [Curiate Assembly, conferred, imperium on magistrates]
-
A.
conferredIn
Indicates that something (such as a degree, title, or honor) was formally granted or awarded within a particular context, event, or institution.
-
B.
conferredOn
chosen
Indicates that something (such as an honor, title, degree, or benefit) has been formally granted or bestowed upon a particular entity.
-
C.
committed
Indicates that an agent has carried out or been responsible for a specific act, event, or wrongdoing.
-
D.
concluded
Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
-
E.
appointed
Indicates that one entity formally assigns another entity to a position, role, or responsibility.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.