Triple
T10776161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Halyard |
E254201
|
entity |
| Predicate | airfieldConstructed |
P89405
|
FINISHED |
| Object | makeshift airstrips near Pranjani |
—
|
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: makeshift airstrips near Pranjani | Statement: [Operation Halyard, airfieldConstructed, makeshift airstrips near Pranjani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airfieldConstructed Context triple: [Operation Halyard, airfieldConstructed, makeshift airstrips near Pranjani]
-
A.
airfieldBuilt
chosen
Indicates that an airfield has been constructed or established, typically specifying who built it, where, and/or when.
-
B.
airfieldRole
Indicates the functional role or operational purpose that an airfield serves within a broader system or context.
-
C.
containsAirfield
Indicates that a location or area includes at least one airfield within its boundaries.
-
D.
airfieldOpened
Indicates that an airfield began operations or was officially opened at a certain time.
-
E.
airfieldDecommissioned
Indicates that an airfield has been officially taken out of service and is no longer used for regular aviation operations.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7329d8c908190bddad40685133ea1 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.