Triple
T14805793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | government of Carthage |
E348030
|
entity |
| Predicate | magistratesMethodOfSelection |
P115795
|
FINISHED |
| Object | election |
—
|
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: election | Statement: [government of Carthage, magistratesMethodOfSelection, election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magistratesMethodOfSelection Context triple: [government of Carthage, magistratesMethodOfSelection, election]
-
A.
hasMagistrateJudges
Indicates that one legal jurisdiction, court, or governing body includes or is served by one or more magistrate judges.
-
B.
jurySelectionMethod
Indicates the process or criteria used to choose individuals who will serve on a jury.
-
C.
judiciaryChosenBy
Indicates that the members of the judiciary are selected or appointed by a specified person, group, or institution.
-
D.
judgesElected
Indicates that the judges in question attained their positions through an electoral process rather than by appointment or other means.
-
E.
magistrateJudgeTerm
Indicates that a magistrate judge holds or serves a specific judicial term or period of office.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf32666081908e84f985c47eb963 |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:34 a.m.