Triple
T34726148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 97 Squadron RAF |
E1001073
|
entity |
| Predicate | airForceGroup |
P78231
|
FINISHED |
| Object | No. 8 Group RAF |
—
|
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: No. 8 Group RAF | Statement: [No. 97 Squadron RAF, airForceGroup, No. 8 Group RAF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airForceGroup Context triple: [No. 97 Squadron RAF, airForceGroup, No. 8 Group RAF]
-
A.
airForceCommand
chosen
Indicates a command relationship in which one entity exercises authority over the operations, organization, or administration of an air force or air force unit.
-
B.
airForceUser
Indicates that an entity is a member of, affiliated with, or acting on behalf of an air force organization.
-
C.
airForceUnitNumber
Indicates the identifying number assigned to an air force unit in a military organizational structure.
-
D.
airForceVariant
Indicates that one entity is a version or model of something specifically adapted for use by an air force.
-
E.
airborneForces
Indicates that military forces are deployed, transported, or operating via aircraft, typically inserted from the air into an operational area.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.