Triple
T26310307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YSL |
E661802
|
entity |
| Predicate | acquisitionPreviousNameOfParent |
P155705
|
FINISHED |
| Object | PPR |
—
|
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: PPR | Statement: [YSL, acquisitionPreviousNameOfParent, PPR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionPreviousNameOfParent Context triple: [YSL, acquisitionPreviousNameOfParent, PPR]
-
A.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
B.
predecessorNameUsage
Indicates that a name was used previously and has been replaced or superseded by a subsequent name in a sequence or lineage.
-
C.
predecessorNameForm
chosen
Indicates that the value is a name or naming form previously used for the same entity before its current name.
-
D.
shortNameOfPredecessor
Indicates that an entity has a predecessor whose abbreviated or shorter name is being specified.
-
E.
laterAcquiredBy
Indicates that one entity was acquired by another entity at a later point in time, after some prior state or ownership.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 10:21 p.m.