Triple
T38043816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staś Tarkowski |
E949560
|
entity |
| Predicate | isProtagonistAlongside |
P32032
|
FINISHED |
| Object | Nel Rawlison |
—
|
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: Nel Rawlison | Statement: [Staś Tarkowski, isProtagonistAlongside, Nel Rawlison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProtagonistAlongside Context triple: [Staś Tarkowski, isProtagonistAlongside, Nel Rawlison]
-
A.
playedAlongside
Indicates that two or more entities participated together at the same time in a shared activity, performance, or event.
-
B.
coProtagonist
chosen
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
C.
hasSecondaryProtagonist
Indicates that an entity (such as a work of fiction) features another character who serves as a secondary or supporting main protagonist alongside the primary one.
-
D.
hasSiblingProtagonists
Indicates that the work features two or more protagonists who are siblings to each other.
-
E.
hasSecondaryProtagonistOccupation
Indicates that a secondary protagonist in a narrative has a specific occupation or job role.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.