Triple
T8989210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Most Expensivest |
E214745
|
entity |
| Predicate | notableGuestAppearances |
P10756
|
FINISHED |
| Object | various celebrities |
—
|
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: various celebrities | Statement: [Most Expensivest, notableGuestAppearances, various celebrities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGuestAppearances Context triple: [Most Expensivest, notableGuestAppearances, various celebrities]
-
A.
notableAppearance
Indicates that an entity is prominently featured or makes a significant appearance in another work, event, or context.
-
B.
notableAppearanceIn
Indicates that an entity is prominently featured or plays a significant role in a particular work, event, or context.
-
C.
hasNotableGuest
chosen
Indicates that an entity has a guest who is distinguished, prominent, or otherwise noteworthy in some significant way.
-
D.
hasNotableMultipleAppearances
Indicates that an entity appears multiple times in a context or medium in a way considered significant or noteworthy.
-
E.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc687205c88190a4cdf12ee2cdfd14 |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.