Triple
T15291370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zenadh Kes |
E365534
|
entity |
| Predicate | hasContemporaryPoliticalIssues |
P25878
|
FINISHED |
| Object | sea rights |
—
|
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: sea rights | Statement: [Zenadh Kes, hasContemporaryPoliticalIssues, sea rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContemporaryPoliticalIssues Context triple: [Zenadh Kes, hasContemporaryPoliticalIssues, sea rights]
-
A.
notableModernIssue
Indicates that the subject is recognized as a significant or widely discussed issue in contemporary times.
-
B.
politicalIssueIn
Indicates that a political issue is relevant to, occurs within, or is associated with a particular geographic or political region.
-
C.
currentPoliticalTrend
Indicates the prevailing direction or pattern of political attitudes, behaviors, or power dynamics at a given time.
-
D.
contemporaryEvents
Indicates that two or more events occur in the same time period or overlap temporally.
-
E.
politicalIssueFor
chosen
Indicates a relationship where a particular topic, problem, or policy area is considered a matter of political concern or debate for a given 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03680b60c8190a3ea54a9d34c8105 |
completed | April 16, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.