Triple
T9541016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier Global Express |
E230155
|
entity |
| Predicate | hasAPU |
P89694
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bombardier Global Express, hasAPU, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAPU Context triple: [Bombardier Global Express, hasAPU, yes]
-
A.
hasApse
Indicates that a structure or building possesses an apse, typically a semicircular or polygonal recess, as one of its architectural features.
-
B.
hasALU
Indicates that an entity includes or is equipped with an Arithmetic Logic Unit (ALU) as a component or functional part.
-
C.
hasOnboardComputer
Indicates that one entity is equipped with or contains an onboard computer system.
-
D.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
E.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
- F. None of above. chosen
Provenance (4 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e695948190ab107fff38c57de7 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:01 p.m.