Triple
T29340783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polecats motorcycle gang |
E744030
|
entity |
| Predicate | associatedWithProtagonist |
P63755
|
FINISHED |
| Object | Ben |
E218629
|
NE 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: Ben | Statement: [Polecats motorcycle gang, associatedWithProtagonist, Ben]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithProtagonist Context triple: [Polecats motorcycle gang, associatedWithProtagonist, Ben]
-
A.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
-
B.
protagonistAllegiance
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
C.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
D.
isFriendOfProtagonist
Indicates that one entity is a friend or close ally of the story’s main character.
-
E.
associatedWithCharacterRole
chosen
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
- F. None of above.
Provenance (4 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25c0ec3f788190a18ef5a6d17094af |
completed | June 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
Created at: April 28, 2026, 1:33 p.m.