Triple
T8590241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU Special Representatives |
E203409
|
entity |
| Predicate | mandateRenewable |
P30609
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [EU Special Representatives, mandateRenewable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mandateRenewable Context triple: [EU Special Representatives, mandateRenewable, true]
-
A.
isRenewable
Indicates that a resource or energy source can be naturally replenished or regenerated within a human-relevant timescale.
-
B.
renews
Indicates that one entity extends, refreshes, or restores the validity, duration, or effectiveness of another entity, often continuing a prior agreement, state, or condition.
-
C.
mandateFrom
Indicates that one entity has been granted authoritative permission or instruction by another entity to act or decide on its behalf.
-
D.
mandateDefinedBy
Indicates that the scope, authority, or responsibilities of one entity’s mandate are formally established or specified by another entity or source.
-
E.
renewalRequired
chosen
Indicates that an existing agreement, status, or authorization must be renewed to remain valid.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.