Triple
T31145225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier CSeries test aircraft |
E793904
|
entity |
| Predicate | testRoles |
P22824
|
FINISHED |
| Object | aerodynamic testing |
—
|
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: aerodynamic testing | Statement: [Bombardier CSeries test aircraft, testRoles, aerodynamic testing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testRoles Context triple: [Bombardier CSeries test aircraft, testRoles, aerodynamic testing]
-
A.
testRole
chosen
Indicates that an entity is assigned or associated with a specific role used for testing or validation purposes.
-
B.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
C.
definesRole
Indicates that one entity specifies or establishes the role, function, or position of another entity within a given context.
-
D.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
E.
usesRoleTypes
Indicates that an entity employs or is associated with specific role classifications or role types within a given context.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.