Triple
T20979979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anne Elliot |
E516731
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Elliot |
—
|
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: Elliot | Statement: [Anne Elliot, familyName, Elliot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elliot Context triple: [Anne Elliot, familyName, Elliot]
-
A.
Elliot
Elliot is the friendly, invisible green dragon who befriends and protects a young orphan boy in Disney’s family film "Pete’s Dragon."
-
B.
Elliot
chosen
Elliot is a surname of English origin borne by various notable individuals, including the family of Charles Elliot.
-
C.
Elliot
Elliot is the given name of Elliot M. See Jr., a U.S. naval aviator, test pilot, and NASA astronaut selected in the early 1960s.
-
D.
Elliot
Elliot is the central protagonist of the horror film "The Bye Bye Man," whose life unravels after he and his friends unwittingly summon a malevolent supernatural entity.
-
E.
Elliot
Elliot is the socially anxious, morphine-addicted cybersecurity engineer and hacker protagonist of the television series "Mr. Robot."
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbdd89f48190b58c67cc1f7968c0 |
completed | April 21, 2026, 4:23 a.m. |
Created at: April 16, 2026, 1:47 p.m.