Triple
T3747451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council resolutions |
E81241
|
entity |
| Predicate | canCallFor |
P2350
|
FINISHED |
| Object | ceasefires |
—
|
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: ceasefires | Statement: [United Nations Security Council resolutions, canCallFor, ceasefires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCallFor Context triple: [United Nations Security Council resolutions, canCallFor, ceasefires]
-
A.
callsFor
chosen
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
B.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
-
D.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
E.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6ac5ac8190934ec1a6c887a8f5 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.