Triple
T24305342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bingo and the Little Woman |
E612518
|
entity |
| Predicate | protagonistFriend |
P78618
|
FINISHED |
| Object | Bingo Little |
—
|
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: Bingo Little | Statement: [Bingo and the Little Woman, protagonistFriend, Bingo Little]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistFriend Context triple: [Bingo and the Little Woman, protagonistFriend, Bingo Little]
-
A.
isFriendOfProtagonist
chosen
Indicates that one entity is a friend or close ally of the story’s main character.
-
B.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
C.
formerSidekick
Indicates that one entity previously served as a sidekick or subordinate companion to another entity, but no longer holds that role.
-
D.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
E.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922641bc81908fa3595941e60741 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:30 a.m.