Triple
T15271749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxar Technologies |
E365035
|
entity |
| Predicate | subsidiary |
P258
|
FINISHED |
| Object | MDA |
E238204
|
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: MDA | Statement: [Maxar Technologies, subsidiary, MDA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MDA Context triple: [Maxar Technologies, subsidiary, MDA]
-
A.
MDA
MDA (Monochrome Display Adapter) is IBM's original text-only video display standard for early IBM PCs, providing high-resolution monochrome output without graphics capabilities.
-
B.
MDA
MDA is the three-letter ISO 3166-1 alpha-3 country code representing the Republic of Moldova.
-
C.
MDA
chosen
MDA is a Canadian space technology company known for developing advanced satellite systems, robotics, and Earth observation solutions.
-
D.
MDA
MDA is the common abbreviation for the Mighty Ducks of Anaheim, a former National Hockey League team based in Anaheim, California.
-
E.
MDA
MDA (Model-Driven Architecture) is a software design approach that emphasizes creating and transforming high-level platform-independent models into platform-specific implementations, standardized by the Object Management Group.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00950a9988190b67dfbc73b8bdbbc |
completed | April 15, 2026, 9:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fee6046a088190a9ebea7672e36b73 |
completed | May 9, 2026, 7:45 a.m. |
Created at: April 10, 2026, 3:14 a.m.