Triple
T35583983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Show and Tell |
E1028297
|
entity |
| Predicate | isBestKnownAsHitFor |
P163740
|
FINISHED |
| Object | Al Wilson |
—
|
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: Al Wilson | Statement: [Show and Tell, isBestKnownAsHitFor, Al Wilson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBestKnownAsHitFor Context triple: [Show and Tell, isBestKnownAsHitFor, Al Wilson]
-
A.
isBestKnownFrom
Indicates that an entity is primarily or most famously recognized in connection with a particular source, context, or work.
-
B.
isWidelyKnownAs
Indicates that an entity is commonly referred to or recognized by a particular name or label by a broad audience.
-
C.
isMostSuccessfulSoloHitOf
chosen
Indicates that one musical work is the most commercially or popularly successful solo hit associated with a particular artist.
-
D.
isKnownPrimarilyByName
Indicates that an entity is chiefly recognized or identified by its name rather than by other attributes or characteristics.
-
E.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.