Triple
T15239822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBDA Germany |
E364224
|
entity |
| Predicate | roleWithinMBDA |
P117700
|
FINISHED |
| Object | national subsidiary for Germany |
—
|
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: national subsidiary for Germany | Statement: [MBDA Germany, roleWithinMBDA, national subsidiary for Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithinMBDA Context triple: [MBDA Germany, roleWithinMBDA, national subsidiary for Germany]
-
A.
roleInAirbus
Indicates that an entity holds or has held a specific role or position within Airbus.
-
B.
roleWithinBoeing
Indicates that one entity holds or has held a specific role, position, or function within the organization Boeing.
-
C.
roleWithinJointBase
Indicates that one entity holds a specific role, function, or position within a joint base shared by multiple organizations or units.
-
D.
roleWithinRaytheon
Indicates that one entity holds or has held a specific role, position, or function within the organization Raytheon.
-
E.
roleInMissions
Indicates the specific function, duty, or position an entity holds within one or more missions.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007db9a148190aadea8d5f8b6b261 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:12 a.m.