Triple
T1703454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Optimates |
E36816
|
entity |
| Predicate | usedPoliticalMethod |
P7603
|
FINISHED |
| Object | senatorial decrees |
—
|
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: senatorial decrees | Statement: [Optimates, usedPoliticalMethod, senatorial decrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPoliticalMethod Context triple: [Optimates, usedPoliticalMethod, senatorial decrees]
-
A.
usedByPolity
Indicates that something (such as a resource, tool, system, or practice) is utilized or employed by a particular polity (e.g., a state, government, or political entity).
-
B.
usedInElection
Indicates that something (such as a resource, tool, or method) was employed or applied as part of conducting an election.
-
C.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
D.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
E.
politicalUse
chosen
Indicates that something is used for political purposes, such as influencing, supporting, or opposing political actors, policies, or processes.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab75ad24408190814069e6e3ef9e59 |
completed | March 7, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69aa61bad17c8190861b92cfb423f68f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.