Triple
T30890885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Queen Bee |
E786892
|
entity |
| Predicate | narrativeRoleOfYoungestBrother |
P101050
|
FINISHED |
| Object | hero |
—
|
LITERAL FINISHED |
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: hero | Statement: [The Queen Bee, narrativeRoleOfYoungestBrother, hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeRoleOfYoungestBrother Context triple: [The Queen Bee, narrativeRoleOfYoungestBrother, hero]
-
A.
youngerBrotherTrait
Indicates that one entity has the characteristic or role of being the younger brother in relation to another entity.
-
B.
youngestBrotherRank
Indicates the ordinal position or rank of an entity among its youngest brothers within a family or sibling group.
-
C.
isBrotherOfProtagonist
Indicates that one person is the male sibling of the story’s main character.
-
D.
narrativeRoleInSeries
Indicates the specific narrative function or role an entity plays within a particular series or serialized work.
-
E.
inNarrativeRole
chosen
Indicates that one entity participates in relation to another by occupying a specific narrative function or role within a story or discourse.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 29, 2026, 8:49 p.m.