Triple
T32872112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNMG2 |
E840819
|
entity |
| Predicate | isOnCallFor |
P175539
|
FINISHED |
| Object | NATO operations |
—
|
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: NATO operations | Statement: [SNMG2, isOnCallFor, NATO operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnCallFor Context triple: [SNMG2, isOnCallFor, NATO operations]
-
A.
canBeCalledOutFor
Indicates that one entity is subject to being criticized, challenged, or held accountable by another for its actions, behavior, or statements.
-
B.
hasCallInNumber
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
-
C.
canBeCalledTo
Indicates that one entity is able or permitted to initiate a call or summon another entity.
-
D.
hasCall
Indicates that one entity initiates or participates in a telephone or voice communication with another entity.
-
E.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: May 1, 2026, 1:17 a.m.