Triple
T7164127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miuccia Prada |
E167023
|
entity |
| Predicate | tookOver |
P8877
|
FINISHED |
| Object | family company Prada in the late 1970s |
—
|
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: family company Prada in the late 1970s | Statement: [Miuccia Prada, tookOver, family company Prada in the late 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOver Context triple: [Miuccia Prada, tookOver, family company Prada in the late 1970s]
-
A.
takesOver
chosen
Indicates that one entity assumes control, ownership, or responsibility for another entity, often replacing its previous controller.
-
B.
tookOverCompanyFrom
Indicates that one entity assumed control or ownership of a company previously controlled or owned by another entity.
-
C.
takenBy
Indicates that something is captured, acquired, or received by a particular entity.
-
D.
overtook
Indicates that one entity moved past and ahead of another that was previously in front, typically while both were in motion.
-
E.
tookPositionOn
Indicates that an entity expressed or adopted a specific stance, opinion, or viewpoint regarding a particular issue, topic, or subject.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e83168a08190937ff46797d94f3e |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.