Triple
T38177042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F.I.S.T. |
E1000242
|
entity |
| Predicate | mainCharacterLaterRole |
P52440
|
FINISHED |
| Object | union boss |
—
|
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: union boss | Statement: [F.I.S.T., mainCharacterLaterRole, union boss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterLaterRole Context triple: [F.I.S.T., mainCharacterLaterRole, union boss]
-
A.
characterFutureRole
chosen
Indicates the role or position that a character is expected or intended to assume at a later point in time.
-
B.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
-
C.
laterMainCharacterOf
Indicates that one entity becomes the main character of a work at a later point in time, succeeding another main character.
-
D.
roleForProtagonist
Indicates the specific narrative or functional role that an entity plays in relation to the story’s main protagonist.
-
E.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:29 p.m.