Triple
T23433962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emilio Pucci |
E563405
|
entity |
| Predicate | successorInBusiness |
P53829
|
FINISHED |
| Object | Laudomia Pucci |
—
|
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: Laudomia Pucci | Statement: [Emilio Pucci, successorInBusiness, Laudomia Pucci]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInBusiness Context triple: [Emilio Pucci, successorInBusiness, Laudomia Pucci]
-
A.
successorInMarket
Indicates that one entity has taken over or followed another in serving the same market or customer base.
-
B.
hasBusinessSuccession
chosen
Indicates that one business entity continues, replaces, or inherits the operations, rights, or obligations of another business over time.
-
C.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
-
D.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
E.
hasCorporateSuccessor
Indicates that one corporate entity is the legal successor to another, inheriting its rights, obligations, or continuity of business.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d9f0d48190903f43d044bcf2dd |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:49 p.m.