Triple
T16611821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robin Williams as Mork |
E403589
|
entity |
| Predicate | reportsTo |
P258
|
FINISHED |
| Object | Orson |
E207527
|
NE 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: Orson | Statement: [Robin Williams as Mork, reportsTo, Orson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orson Context triple: [Robin Williams as Mork, reportsTo, Orson]
-
A.
Orson
chosen
Orson is a masculine given name most famously associated with the American filmmaker and actor Orson Welles.
-
B.
Orrin
Orrin is a masculine given name most notably borne by long-serving U.S. Senator Orrin Hatch of Utah.
-
C.
Orson Pink
Orson Pink is a time-traveling descendant of Danny Pink and Clara Oswald who appears in the British science fiction series Doctor Who.
-
D.
Osborn
Osborn is a surname and given name of English origin, borne by various notable individuals across fields such as politics, science, and the arts.
-
E.
Willard
Willard is a masculine given name of Old English origin meaning "resolute" or "strong-willed."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e36096356c819092815d64db041793 |
completed | April 18, 2026, 10:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0075aca5c0819092637e0d83ce8ac0 |
completed | May 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 5:17 a.m.