Triple
T2370791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danaher Corporation |
E46084
|
entity |
| Predicate | hasBusinessOperation |
P37857
|
FINISHED |
| Object | life sciences instruments |
—
|
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: life sciences instruments | Statement: [Danaher Corporation, hasBusinessOperation, life sciences instruments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusinessOperation Context triple: [Danaher Corporation, hasBusinessOperation, life sciences instruments]
-
A.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
B.
hasBusinessRoute
Indicates that there exists an established commercial or service route connecting two business-related entities.
-
C.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
D.
hasGlobalOperationsIn
Indicates that an entity conducts business or operational activities across multiple countries within the specified region or location.
-
E.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76f5aec8190867d621e6849258c |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6443c6c8190b932de2abd8eb28f |
completed | March 7, 2026, 6:31 a.m. |
Created at: March 4, 2026, 7:56 p.m.