Triple
T18375093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tallil Air Base |
E446290
|
entity |
| Predicate | wasExpandedBy |
P5633
|
FINISHED |
| Object | United States military after 2003 |
—
|
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: United States military after 2003 | Statement: [Tallil Air Base, wasExpandedBy, United States military after 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasExpandedBy Context triple: [Tallil Air Base, wasExpandedBy, United States military after 2003]
-
A.
wasExpanded
Indicates that something increased in size, scope, or extent compared to its previous state.
-
B.
expandedBy
chosen
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
C.
wasExtendedTo
Indicates that something previously existing was lengthened, expanded, or prolonged to reach a new limit, scope, or duration.
-
D.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
E.
significantlyExpandedUnder
Indicates that something grew or increased to a much greater extent during the period or context defined by 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51757a75c8190814db973ae1a86cd |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.