Triple
T23544066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesse deWilde |
E577838
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Jesse |
—
|
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: Jesse | Statement: [Jesse deWilde, givenName, Jesse]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jesse Context triple: [Jesse deWilde, givenName, Jesse]
-
A.
Jesse
Jesse is the nickname of Jesse Owens, the legendary American track and field athlete who won four gold medals at the 1936 Berlin Olympics.
-
B.
Jesse
chosen
Jesse is a common given name used for people of all genders in various cultures, often associated with Hebrew origins meaning "gift" or "God exists."
-
C.
Jesse
Jesse is the young boy who befriends and helps free the captive orca in the family film "Free Willy."
-
D.
Jesse
Jesse is a prominent Urhobo clan and town in Delta State, Nigeria, known for its cultural heritage and role within the Urhobo ethnic group.
-
E.
Jesse
Jesse is the customizable protagonist and central hero of the narrative-driven adventure game Minecraft: Story Mode.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1ef55c8190a93c33e704ec3b5a |
completed | April 29, 2026, 7:07 a.m. |
Created at: April 17, 2026, 6:11 p.m.