Triple
T18755528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Libertine (stage performance) |
E458638
|
entity |
| Predicate | protagonistSocialRole |
P123132
|
FINISHED |
| Object | rake |
—
|
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: rake | Statement: [The Libertine (stage performance), protagonistSocialRole, rake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistSocialRole Context triple: [The Libertine (stage performance), protagonistSocialRole, rake]
-
A.
protagonistSocialType
chosen
Indicates the type of social role, status, or interaction style that the protagonist has within the context of the narrative or scenario.
-
B.
protagonistSocialStatus
Indicates the social standing or class position held by the story’s main character in relation to others in their society.
-
C.
featuresProtagonistOccupation
Indicates that the work’s main character has a specified occupation or job role.
-
D.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
E.
protagonistDescription
Indicates that a text provides a descriptive summary or characterization of the story’s 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579f084208190a4b3563d47154e69 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.