Triple
T37401697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batman Beyond |
E929010
|
entity |
| Predicate | mentorOfProtagonist |
P106997
|
FINISHED |
| Object | Bruce Wayne |
—
|
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: Bruce Wayne | Statement: [Batman Beyond, mentorOfProtagonist, Bruce Wayne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentorOfProtagonist Context triple: [Batman Beyond, mentorOfProtagonist, Bruce Wayne]
-
A.
mentorCharacter
chosen
Indicates that one character serves as a mentor, providing guidance, teaching, or support to another character.
-
B.
mentorOrPartner
Indicates a relationship in which one entity either provides guidance and support to another as a mentor or collaborates with them on relatively equal footing as a partner.
-
C.
mentorOrAppointer
Indicates a relationship where one entity either serves as a mentor to another or is responsible for appointing that entity to a role or position.
-
D.
mentorType
Indicates the specific role or category of mentorship that one entity provides to another.
-
E.
coachInStory
Indicates that one entity serves as a coach for another entity within the context of a specific story or 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.