Triple
T11073553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danaher Corporation |
E261807
|
entity |
| Predicate | stockTicker |
P1447
|
FINISHED |
| Object | DHR |
E261807
|
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: DHR | Statement: [Danaher Corporation, stockTicker, DHR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DHR Context triple: [Danaher Corporation, stockTicker, DHR]
-
A.
DHR
chosen
DHR is the stock ticker symbol for Danaher Corporation, a global science and technology company focused on life sciences, diagnostics, and environmental and applied solutions.
-
B.
DHN
DHN is the IATA airport code for Dothan Regional Airport serving the Dothan, Alabama area in the United States.
-
C.
RDH
RDH is the National Rail station code for Redhill railway station in Surrey, England.
-
D.
DHM
DHM is the commonly used abbreviation for the German Historical Museum in Berlin, a major institution dedicated to documenting and presenting German history.
-
E.
DH
DH is the postcode area covering Durham and surrounding parts of North East England in the United Kingdom.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994e32fc8190a6591d9e82b68f75 |
completed | April 9, 2026, 12:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3c8bfb0c88190be27f5ce09b02c8b |
completed | April 18, 2026, 6:09 p.m. |
Created at: April 8, 2026, 9:26 p.m.