Triple
T29259626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phillips-Van Heusen Corporation |
E741803
|
entity |
| Predicate | acquisitionOfTommyHilfiger |
P158001
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Phillips-Van Heusen Corporation, acquisitionOfTommyHilfiger, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfTommyHilfiger Context triple: [Phillips-Van Heusen Corporation, acquisitionOfTommyHilfiger, 2010]
-
A.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
B.
wasAcquiredIn
chosen
Indicates that one entity obtained ownership or control of another entity through an acquisition event that occurred at a specific time or in a specific transaction.
-
C.
acquiredByBlueCo
Indicates that one entity has been purchased or taken over in an acquisition by the company BlueCo.
-
D.
acquiredWith
Indicates that one entity was obtained, purchased, or gained together with or by means of another entity.
-
E.
couldBeAcquiredBy
Indicates that one entity is a potential target to be obtained, bought, or taken over by another entity.
- 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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 12:40 p.m.