Triple
T33233958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Refrigerator |
E850775
|
entity |
| Predicate | mediaNicknameOf |
P17599
|
FINISHED |
| Object | William Perry |
—
|
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: William Perry | Statement: [The Refrigerator, mediaNicknameOf, William Perry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaNicknameOf Context triple: [The Refrigerator, mediaNicknameOf, William Perry]
-
A.
mediaNicknameGivenBy
chosen
Indicates that a particular nickname was assigned to an entity by media organizations or outlets.
-
B.
mediaNicknameOrigin
Indicates that a media-related nickname originates from, or is derived based on, a particular source or context.
-
C.
screenName
Indicates the display or handle name associated with an entity, typically used as its visible identifier in user interfaces or social platforms.
-
D.
mediaName
Indicates the name or title assigned to a media item (such as a work, file, or publication) in the relationship.
-
E.
lineNickname
Indicates that one entity is an alternative or informal name (nickname) used to refer to a particular line (such as a route, service, or connection).
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:31 a.m.