Triple
T19649912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 72 Squadron RAF |
E471781
|
entity |
| Predicate | airForceUnitNumber |
P136830
|
FINISHED |
| Object | 72 |
—
|
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: 72 | Statement: [No. 72 Squadron RAF, airForceUnitNumber, 72]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airForceUnitNumber Context triple: [No. 72 Squadron RAF, airForceUnitNumber, 72]
-
A.
airForceDesignation
Indicates that one entity is the official designation or code assigned to something by an air force.
-
B.
airForceDesignationUser
Indicates that an entity uses or is assigned a specific air force designation.
-
C.
airForceUser
Indicates that an entity is a member of, affiliated with, or acting on behalf of an air force organization.
-
D.
airForceServiceNumber
Indicates the unique identification number assigned to an individual for their service in an air force.
-
E.
primaryUSAAFUnit
Indicates that one entity is the main or principal United States Army Air Forces unit associated with, responsible for, or assigned to the other entity.
- F. None of above. chosen
Provenance (4 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641286bbc8190886f309de13063bf |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.