Triple
T8133181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Orville |
E189901
|
entity |
| Predicate | crewMember |
P2094
|
FINISHED |
| Object | Yaphit |
E630746
|
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: Yaphit | Statement: [USS Orville, crewMember, Yaphit]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yaphit Context triple: [USS Orville, crewMember, Yaphit]
-
A.
Yaphit
chosen
Yaphit is a gelatinous, shape-shifting engineer serving aboard the exploratory spaceship in the science-fiction TV series "The Orville."
-
B.
Shem
Shem is a biblical figure regarded as one of Noah’s sons and traditionally considered an ancestor of the Semitic peoples.
-
C.
Reuel
Reuel is a biblical figure identified as another name for Jethro, the Midianite priest and father-in-law of Moses.
-
D.
Reuel
Reuel is the middle name of famed English author and philologist J. R. R. Tolkien, used as part of his full name John Ronald Reuel Tolkien.
-
E.
Enosh
Enosh is a biblical figure recognized as a grandson of Adam and an early patriarch in the Book of Genesis.
- 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb43ba98c881909c4b4c9cd25ad063 |
completed | March 31, 2026, 3:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc9488f0bc8190a4fdf6d021f54e13 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 5:35 p.m.