Triple
T28977343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | بنينة |
E734447
|
entity |
| Predicate | النظام_السياسي_للدولة |
P220
|
FINISHED |
| Object | الجمهورية الليبية |
—
|
NE NERFINISHED |
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: الجمهورية الليبية | Statement: [بنينة, النظام_السياسي_للدولة, الجمهورية الليبية]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: النظام_السياسي_للدولة Context triple: [بنينة, النظام_السياسي_للدولة, الجمهورية الليبية]
-
A.
associatedPoliticalSystem
Indicates that there exists a political system with which the subject is formally or conceptually connected.
-
B.
politicalFramework
Indicates the overarching system of political structures, principles, and rules that organize and govern relationships and decision-making within a society or institution.
-
C.
typeOfPolity
Indicates that one entity is a political unit and the other specifies the kind or classification of that polity (e.g., empire, kingdom, republic).
-
D.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
E.
politicalForm
Indicates the type or structure of governance or political organization that characterizes an entity.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ee1cc508190bc979963e3589271 |
completed | May 2, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:09 a.m.