Triple
T112236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Aerobatic Team Red Arrows |
E2272
|
entity |
| Predicate | teamSizePilots |
P3668
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [RAF Aerobatic Team Red Arrows, teamSizePilots, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamSizePilots Context triple: [RAF Aerobatic Team Red Arrows, teamSizePilots, 9]
-
A.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
B.
typicalTeamSize
chosen
Indicates the usual or most common number of members that make up a given team.
-
C.
airGroupSize
Indicates the number of units or elements grouped together in an air-related context (such as aircraft in a formation or air assets in an operation).
-
D.
fleetSize
Indicates the total number of vehicles, vessels, or units that collectively make up a fleet associated with an entity.
-
E.
hasAerobaticDisplayTeam
Indicates that an entity maintains or is associated with a team that performs aerobatic flying displays.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.