Triple
T10042141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation IRINI |
E205319
|
entity |
| Predicate | hasDurationType |
P91794
|
FINISHED |
| Object | renewable fixed-term mandate |
—
|
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: renewable fixed-term mandate | Statement: [Operation IRINI, hasDurationType, renewable fixed-term mandate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDurationType Context triple: [Operation IRINI, hasDurationType, renewable fixed-term mandate]
-
A.
hasOfficialDuration
Indicates the formally defined length of time associated with an event, process, or entity.
-
B.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
C.
possibleDuration
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
-
D.
hasTrailDuration
Indicates that an entity (such as a trail or route) is associated with a specific amount of time required to traverse or complete it.
-
E.
hasAllegedDuration
Indicates that a specified length of time is claimed or reported for something, but not confirmed as factual.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee48d8c8190af7c93b60f8ca7cb |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:55 p.m.