Triple
T804945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honey Science LLC |
E17409
|
entity |
| Predicate | acquisitionCompletedIn |
P15703
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Honey Science LLC, acquisitionCompletedIn, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionCompletedIn Context triple: [Honey Science LLC, acquisitionCompletedIn, 2020]
-
A.
acquisitionCompletedYear
chosen
Indicates the calendar year in which an acquisition transaction was fully completed.
-
B.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
C.
acquisitionDate
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
D.
acquisition
Indicates the act or relationship in which one entity obtains ownership or control of another entity, asset, or resource.
-
E.
acquisitionType
Indicates the specific kind or category of acquisition relationship that exists between entities (such as a company buying another company, assets, or a controlling stake).
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ace495348190aec66f35ea90bc89 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa70973c8190adbf08302d1103a9 |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.