Triple
T5478755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTX Corporation |
E123419
|
entity |
| Predicate | GICSIndustry |
P14918
|
FINISHED |
| Object | Aerospace & Defense |
—
|
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: Aerospace & Defense | Statement: [RTX Corporation, GICSIndustry, Aerospace & Defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GICSIndustry Context triple: [RTX Corporation, GICSIndustry, Aerospace & Defense]
-
A.
industryOfUnderlyingCompany
Indicates the industry sector in which the underlying company associated with this entity operates.
-
B.
hasGICSSubIndustry
chosen
Indicates that an entity is classified within a specific GICS (Global Industry Classification Standard) sub-industry category.
-
C.
SICCode
Indicates the standardized industrial classification code that categorizes the primary type of economic activity associated with an entity or relationship.
-
D.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
E.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
- F. None of above.
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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.