Triple
T16295618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 29 Squadron RAF |
E395637
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | 29 Squadron |
E395637
|
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: 29 Squadron | Statement: [No. 29 Squadron RAF, alsoKnownAs, 29 Squadron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 29 Squadron Context triple: [No. 29 Squadron RAF, alsoKnownAs, 29 Squadron]
-
A.
29 Squadron
chosen
29 Squadron is a Royal Air Force fighter squadron historically known for its air defense and combat roles in both World Wars and beyond.
-
B.
349 Squadron
349 Squadron is a Belgian Air Component fighter squadron known for its long operational history and participation in NATO air defense and international missions.
-
C.
10 Squadron
10 Squadron is a Royal Air Force flying unit historically known for its roles in bomber and transport operations.
-
D.
207 Squadron
207 Squadron is a Royal Air Force unit with a long history dating back to World War I, known for its roles in bomber and training operations.
-
E.
141 Squadron
141 Squadron was a Royal Air Force fighter unit best known for its night-fighter operations during the Second World War.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2d08108190bab1b3325923af1d |
completed | April 17, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f9b42248190a3c8c2647a42aeb9 |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 10, 2026, 5:06 a.m.