Triple
T27942828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 12 Squadron RFC |
E700797
|
entity |
| Predicate | airForcePredecessor |
P137432
|
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: [No. 12 Squadron RFC, airForcePredecessor, Royal Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airForcePredecessor Context triple: [No. 12 Squadron RFC, airForcePredecessor, Royal Air Force]
-
A.
militaryBranchPredecessorOf
chosen
Indicates that one military branch served as the organizational or historical predecessor to another military branch.
-
B.
airForceEquivalent
Indicates that one military unit, rank, or asset is the corresponding or analogous counterpart within an air force to another entity in a different branch or context.
-
C.
militaryBranchAssociatedWith
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
-
D.
usedByAirForce
Indicates that something is employed, operated, or otherwise utilized by an air force.
-
E.
hasMilitaryWingHistory
Indicates that an entity has, or has had in the past, an associated military wing or armed branch as part of its history.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:19 p.m.