Triple
T36420471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Cross to Guy Gibson |
E897138
|
entity |
| Predicate | relatedSquadronBase |
P204868
|
FINISHED |
| Object | RAF Scampton |
E26508
|
NE 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: RAF Scampton | Statement: [Victoria Cross to Guy Gibson, relatedSquadronBase, RAF Scampton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedSquadronBase Context triple: [Victoria Cross to Guy Gibson, relatedSquadronBase, RAF Scampton]
-
A.
squadron
Indicates that an entity is organized into or associated with a specific squadron as a formal operational unit.
-
B.
squadronSystem
Indicates a relationship where an entity functions as or is part of the system, organization, or structure associated with a particular squadron.
-
C.
squadronCode
Indicates the identifying code assigned to a military or aviation squadron that denotes its unit designation.
-
D.
relatedMilitaryUnit
Indicates that there is an association or connection between two military units, such as organizational, operational, or historical linkage.
-
E.
numberOfSquadronsInParentUnit
Indicates the total count of squadrons that are contained within or assigned to a given parent unit.
- F. None of above. chosen
Provenance (5 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afc52bbc81909f068dbb4a16dd89 |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.