Triple
T8312025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Gracchus |
E194611
|
entity |
| Predicate | proposedLaw |
P82691
|
FINISHED |
| Object | lex frumentaria |
—
|
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: lex frumentaria | Statement: [Gaius Gracchus, proposedLaw, lex frumentaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedLaw Context triple: [Gaius Gracchus, proposedLaw, lex frumentaria]
-
A.
governmentFormProposed
Indicates that a particular form or structure of government has been put forward as a proposal by an entity.
-
B.
proposedAmendment
Indicates that one entity has formally suggested a change or addition (an amendment) to another entity, such as a document, law, or agreement.
-
C.
passedLegislation
Indicates that a governing body has formally approved and enacted a specific piece of legislation or law.
-
D.
relatedLegislation
Indicates that there exists a legislative document that is connected to, affects, or is otherwise relevant to the subject entity.
-
E.
areaOfLegislation
Indicates that one entity defines, concerns, or governs the legal domain or subject matter covered by another entity.
- F. None of above. chosen
Provenance (4 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f504ca8819087fb1f731f7a7cfd |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:54 p.m.