Triple
T25706252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Have Plenty of Fun |
E644596
|
entity |
| Predicate | mainCharactersGroupName |
P107636
|
FINISHED |
| Object | Famous Five |
—
|
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: Famous Five | Statement: [Five Have Plenty of Fun, mainCharactersGroupName, Famous Five]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharactersGroupName Context triple: [Five Have Plenty of Fun, mainCharactersGroupName, Famous Five]
-
A.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
-
B.
titleCharacterGroup
chosen
Indicates that a group of characters is associated with or featured in the title of a work.
-
C.
notableCharacterGroup
Indicates that a group of characters is especially prominent, significant, or noteworthy within a given context or work.
-
D.
associatedCharacters
Indicates that two or more characters are linked or connected through some relationship, involvement, or relevance to each other.
-
E.
mainProtagonistTeamMember
Indicates that an entity is a member of the primary team or group associated with the main protagonist.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 9:05 p.m.