Triple
T7870294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Security Council Resolution 1386 |
E182719
|
entity |
| Predicate | requestedReportsFrom |
P12767
|
FINISHED |
| Object | ISAF leadership |
—
|
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: ISAF leadership | Statement: [United Nations Security Council Resolution 1386, requestedReportsFrom, ISAF leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestedReportsFrom Context triple: [United Nations Security Council Resolution 1386, requestedReportsFrom, ISAF leadership]
-
A.
requiresReportFrom
chosen
Indicates that one entity is obligated to obtain or receive a report from another entity.
-
B.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
C.
requiredReportOn
Indicates that one entity is obligated to produce or submit a report concerning another entity or subject.
-
D.
reportsThrough
Indicates that one entity formally communicates and is accountable to another entity through an established reporting or supervisory chain.
-
E.
requiresReportTo
Indicates that one entity is obligated to submit or provide a report to another 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb384a285881908a5b2de278f9556f |
completed | March 31, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:55 p.m.