Triple
T25706261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Have Plenty of Fun |
E644596
|
entity |
| Predicate | protagonistGroupComposition |
P24067
|
FINISHED |
| Object | four children and a dog |
—
|
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: four children and a dog | Statement: [Five Have Plenty of Fun, protagonistGroupComposition, four children and a dog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistGroupComposition Context triple: [Five Have Plenty of Fun, protagonistGroupComposition, four children and a dog]
-
A.
hasProtagonistGroup
chosen
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
-
B.
mainProtagonistTeamMember
Indicates that an entity is a member of the primary team or group associated with the main protagonist.
-
C.
protagonistCount
Indicates the number of primary protagonists involved in a given narrative or work.
-
D.
protagonistAllegiance
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
E.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
- 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_69f5fc113b40819088a0d53c824097e4 |
completed | May 2, 2026, 1:28 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:05 p.m.