Triple
T1591358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Security Assistance Force |
E34184
|
entity |
| Predicate | peakTroopStrengthDate |
P17244
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [International Security Assistance Force, peakTroopStrengthDate, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakTroopStrengthDate Context triple: [International Security Assistance Force, peakTroopStrengthDate, 2011]
-
A.
peakTroopDeployment
chosen
Indicates the maximum number of troops that were deployed at any single point during a specified conflict or operation.
-
B.
personnelStrength
Indicates the number or capacity of people assigned to or available for a particular unit, organization, or operation.
-
C.
movementDate
Indicates the date on which a movement, transfer, or relocation event occurs.
-
D.
peakDayAttendance
Indicates the number of attendees present on the single highest-attendance day within a given period or event.
-
E.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.