Triple
T20480895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Cottesmore |
E502447
|
entity |
| Predicate | roleInHarrierForce |
P9463
|
FINISHED |
| Object | main operating base for Joint Force Harrier |
—
|
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: main operating base for Joint Force Harrier | Statement: [RAF Cottesmore, roleInHarrierForce, main operating base for Joint Force Harrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInHarrierForce Context triple: [RAF Cottesmore, roleInHarrierForce, main operating base for Joint Force Harrier]
-
A.
roleInAH64
Indicates that an entity has a specific functional role or position in relation to the AH-64 attack helicopter.
-
B.
roleDuringBlackHawkWar
Indicates the specific role, position, or function an entity held during the Black Hawk War.
-
C.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
D.
roleInMissions
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
E.
HodRole
Indicates that an entity holds the role or position of Head of Department (HOD) in relation to a specified department or organizational unit.
- 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_69e0b4af32848190aea80682b44d5d6e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69b56dd248190b6bc4e513aff3c9c |
completed | April 20, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:34 a.m.