Triple
T28480698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISAF in Afghanistan |
E720681
|
entity |
| Predicate | expandedBeyond |
P53166
|
FINISHED |
| Object | Kabul |
—
|
NE NERFINISHED |
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: Kabul | Statement: [ISAF in Afghanistan, expandedBeyond, Kabul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedBeyond Context triple: [ISAF in Afghanistan, expandedBeyond, Kabul]
-
A.
extendsBeyond
chosen
Indicates that one entity continues past or surpasses the spatial, temporal, or conceptual limits of another entity.
-
B.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
C.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
-
D.
expandedWithin
Indicates that one entity has grown, unfolded, or extended its presence or scope inside the spatial or conceptual boundaries of another entity.
-
E.
expandedAfter
Indicates that one entity increases in size, scope, or extent after another specified event or point in time.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 2:55 a.m.