Triple
T36995961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAG-26 |
E915227
|
entity |
| Predicate | notableComponentUnitType |
P6678
|
FINISHED |
| Object | Marine Medium Tiltrotor Squadron |
E398937
|
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: Marine Medium Tiltrotor Squadron | Statement: [MAG-26, notableComponentUnitType, Marine Medium Tiltrotor Squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableComponentUnitType Context triple: [MAG-26, notableComponentUnitType, Marine Medium Tiltrotor Squadron]
-
A.
componentUnit
Indicates that one entity functions as a constituent or sub-unit that forms part of a larger composite entity.
-
B.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
-
C.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
D.
notableStudioUnit
Indicates a relationship where a particular studio unit is recognized as notable or significant in connection with the subject.
-
E.
componentType
chosen
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
- F. None of above.
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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e57629afc819098bc33f57d1d5369 |
completed | June 26, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.