Triple
T31755327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anyone Can Cook |
E810541
|
entity |
| Predicate | referencedByCharacter |
P60518
|
FINISHED |
| Object | Anton Ego |
—
|
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: Anton Ego | Statement: [Anyone Can Cook, referencedByCharacter, Anton Ego]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referencedByCharacter Context triple: [Anyone Can Cook, referencedByCharacter, Anton Ego]
-
A.
refersToCharacter
chosen
Indicates that one entity makes reference to, mentions, or points to a specific character as its subject.
-
B.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
C.
givenByCharacter
Indicates that something (such as an item, information, or assistance) is provided or handed over by a particular character.
-
D.
usedByOtherCharacters
Indicates that the entity is utilized, employed, or otherwise made use of by one or more other characters.
-
E.
representedByCharacter
Indicates that one entity is depicted, symbolized, or personified by a particular character in a work or medium.
- F. None of above.
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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 30, 2026, 11:29 p.m.