Triple
T33414096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Password |
E855665
|
entity |
| Predicate | hasCelebrityGuest |
P10756
|
FINISHED |
| Object | Tom Poston |
—
|
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: Tom Poston | Statement: [Password, hasCelebrityGuest, Tom Poston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCelebrityGuest Context triple: [Password, hasCelebrityGuest, Tom Poston]
-
A.
hasGuestAppearances
Indicates that an entity features one or more appearances by another entity in a guest capacity.
-
B.
hasNotableGuest
chosen
Indicates that an entity has a guest who is distinguished, prominent, or otherwise noteworthy in some significant way.
-
C.
hasNotableGuestRole
Indicates that an entity appears in a significant but non-starring guest role in relation to another entity, such as a show, episode, or production.
-
D.
guestStar
Indicates that one entity appears in a limited, special, or featured role within another entity’s production, event, or context, without being a regular or primary participant.
-
E.
wasGuestHostOf
Indicates that one entity temporarily served as a guest host for another entity’s show, program, or event.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 1, 2026, 1:36 a.m.