Triple
T31299802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Fashion |
E798183
|
entity |
| Predicate | isPartOfPrinceLegacy |
P196750
|
FINISHED |
| Object | Prince’s musical legacy |
—
|
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: Prince’s musical legacy | Statement: [High Fashion, isPartOfPrinceLegacy, Prince’s musical legacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfPrinceLegacy Context triple: [High Fashion, isPartOfPrinceLegacy, Prince’s musical legacy]
-
A.
hadPrincelyComponents
Indicates that something included or was composed of elements associated with princely status, rank, or attributes.
-
B.
holderIsPrince
Indicates that the holder of something has the royal status or title of a prince.
-
C.
princessOf
Indicates that one entity holds the royal title or role of princess in relation to another entity, typically a realm, family, or sovereign.
-
D.
viewOfPrince
Indicates a visual representation or perspective specifically depicting the prince.
-
E.
coPrince
Indicates a relationship in which two or more individuals simultaneously share and exercise the rank and authority of prince over the same domain or polity.
- F. None of above. chosen
Provenance (4 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69fe673905408190a2ae68c2c9563403 |
completed | May 8, 2026, 10:44 p.m. |
Created at: April 29, 2026, 9:14 p.m.