Triple
T20350232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EarthBound |
E495985
|
entity |
| Predicate | playableCharacter |
P43877
|
FINISHED |
| Object | Ness |
—
|
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: Ness | Statement: [EarthBound, playableCharacter, Ness]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ness Context triple: [EarthBound, playableCharacter, Ness]
-
A.
Ness
Ness is a small village in the civil parish of Neston on the Wirral Peninsula in Cheshire, England.
-
B.
Ness
Ness is a surname most famously associated with Eliot Ness, the American Prohibition agent who led the "Untouchables" in combating organized crime in Chicago.
-
C.
Ness
Ness is a remote crofting and fishing community at the northern tip of the Isle of Lewis in Scotland’s Outer Hebrides.
-
D.
Ness
chosen
Ness is a young boy with psychic powers and a baseball bat who serves as the protagonist of the cult-classic role-playing game EarthBound.
-
E.
Olimar
Olimar is the diminutive spacefaring captain from the Pikmin video game series who commands and relies on Pikmin to survive and complete his missions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6784eacf4819095504e541d1d284d |
completed | April 20, 2026, 7:02 p.m. |
Created at: April 16, 2026, 11:24 a.m.