Triple
T5162072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 207 Squadron RAF |
E116457
|
entity |
| Predicate | airForceNumbering |
P44071
|
FINISHED |
| Object | numbered 207 |
—
|
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: numbered 207 | Statement: [No. 207 Squadron RAF, airForceNumbering, numbered 207]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airForceNumbering Context triple: [No. 207 Squadron RAF, airForceNumbering, numbered 207]
-
A.
airForceDesignation
Indicates that one entity is the official designation or code assigned to something by an air force.
-
B.
airForceServiceNumber
Indicates the unique identification number assigned to an individual for their service in an air force.
-
C.
fleetNumbers
chosen
Indicates that there is an association between an entity and one or more identifying numbers assigned to it as part of a fleet.
-
D.
aircraftDesignationPrefix
Indicates the standardized prefix used in an aircraft’s designation that conveys its type, role, or function.
-
E.
aircraftMarking
Indicates a relationship where a marking, symbol, or identifier is applied to or displayed on an aircraft.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79268ea48190a22d3350babc153c |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.