Triple
T14805984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carthaginian administration |
E348034
|
entity |
| Predicate | popularAssemblyRole |
P79768
|
FINISHED |
| Object | ratified major decisions |
—
|
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: ratified major decisions | Statement: [Carthaginian administration, popularAssemblyRole, ratified major decisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularAssemblyRole Context triple: [Carthaginian administration, popularAssemblyRole, ratified major decisions]
-
A.
popularVoteRole
Indicates the role or capacity in which an entity participates in or is associated with a popular vote.
-
B.
roleInAssembly
chosen
Indicates the specific function, position, or responsibility an entity holds within a particular assembly or gathering.
-
C.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
D.
representedRole
Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
-
E.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
- 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_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. |
Created at: April 10, 2026, 1:35 a.m.