Triple
T27684770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CASC |
E697997
|
entity |
| Predicate | hasSubsidiariesIn |
P189423
|
FINISHED |
| Object | launch vehicle manufacturing |
—
|
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: launch vehicle manufacturing | Statement: [CASC, hasSubsidiariesIn, launch vehicle manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsidiariesIn Context triple: [CASC, hasSubsidiariesIn, launch vehicle manufacturing]
-
A.
hasSubsidiaryBusiness
Indicates that one business entity owns or controls another business entity as its subsidiary.
-
B.
hasSubsidiaryLabel
Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
-
C.
hasSubsidiaryTop
Indicates that one organization is the primary or top-level parent of another organization that operates as its subsidiary.
-
D.
hasAllianceThroughSubsidiary
Indicates that two entities are in an alliance indirectly, established or maintained through one or more subsidiary entities rather than directly between the primary entities.
-
E.
hasSubsidiaryFounded
Indicates that one entity has a subsidiary that was founded or established by another specified entity.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 27, 2026, 2:48 p.m.