Triple
T32412236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liverpool (Speke) Airport |
E828255
|
entity |
| Predicate | militaryCo‑user |
P123900
|
FINISHED |
| Object | Royal Air Force |
—
|
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: Royal Air Force | Statement: [Liverpool (Speke) Airport, militaryCo‑user, Royal Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCo‑user Context triple: [Liverpool (Speke) Airport, militaryCo‑user, Royal Air Force]
-
A.
militaryBaseUser
chosen
Indicates that one entity uses, operates, or is stationed at a particular military base.
-
B.
usesMilitaryUnit
Indicates that one entity employs, deploys, or otherwise makes operational use of a specific military unit.
-
C.
militaryProject
Indicates a project that is conducted, funded, or controlled by a military organization, typically for defense, security, or warfare-related purposes.
-
D.
coordinatesMilitaryOperationsOf
Indicates having authority to plan, direct, and manage the military operations carried out by another entity.
-
E.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 1, 2026, 12:53 a.m.