Triple
T36571285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veralto Corporation |
E902128
|
entity |
| Predicate | hasParentCompanyBeforeSpinOff |
P5815
|
FINISHED |
| Object | Danaher Corporation |
—
|
NE NERFINISHED |
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: Danaher Corporation | Statement: [Veralto Corporation, hasParentCompanyBeforeSpinOff, Danaher Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentCompanyBeforeSpinOff Context triple: [Veralto Corporation, hasParentCompanyBeforeSpinOff, Danaher Corporation]
-
A.
hasParentCompany
Indicates that one company is owned or controlled by another company that serves as its parent organization.
-
B.
parentCompanyAtTime
Indicates that one company is the parent (controlling) company of another during a specified time period.
-
C.
parentCompanyAtStartOfPeriod
Indicates that one entity was the parent company of another at the beginning of a specified time period.
-
D.
hasParentCompanyOrigin
Indicates that an entity’s parent company originates from, or was founded in, a specified location or jurisdiction.
-
E.
formerParentCompany
chosen
Indicates that one entity previously served as the parent company of another but no longer holds that status.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: May 3, 2026, 4:11 p.m.