Triple
T15857182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonardo DRS, Inc. |
E384489
|
entity |
| Predicate | stockTicker |
P1447
|
FINISHED |
| Object | DRS |
E384489
|
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: DRS | Statement: [Leonardo DRS, Inc., stockTicker, DRS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DRS Context triple: [Leonardo DRS, Inc., stockTicker, DRS]
-
A.
DRS
chosen
DRS is the stock ticker symbol for Leonardo DRS, an American defense technology company specializing in advanced military and intelligence systems.
-
B.
DRS
DRS is the three-letter IATA airport code for Dresden Airport in Dresden, Germany.
-
C.
DRS Technologies
DRS Technologies was a U.S.-based defense and aerospace company specializing in military electronics and integrated systems, later rebranded as Leonardo DRS after its acquisition by the Italian defense group Leonardo.
-
D.
DR1
DR1 is Denmark’s primary national television channel, operated by the public broadcaster DR and known for producing high-quality Danish drama and news programming.
-
E.
DR3
DR3 is a Danish television channel operated by the public broadcaster DR, primarily targeting younger audiences with contemporary entertainment, series, and cultural programming.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1555808688190882b610109d1e5f4 |
completed | April 16, 2026, 9:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa14c1e508190a182db216cc4e326 |
completed | May 9, 2026, 9:04 p.m. |
Created at: April 10, 2026, 4:50 a.m.