Triple
T23954389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter O'Toole as Prince Meleagre |
E603741
|
entity |
| Predicate | characterSocialStatus |
P62272
|
FINISHED |
| Object | prince |
—
|
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: prince | Statement: [Peter O'Toole as Prince Meleagre, characterSocialStatus, prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterSocialStatus Context triple: [Peter O'Toole as Prince Meleagre, characterSocialStatus, prince]
-
A.
protagonistSocialStatus
Indicates the social standing or class position held by the story’s main character in relation to others in their society.
-
B.
subjectSocialStatus
chosen
Indicates the social standing or rank that the subject holds within a society or group.
-
C.
possibleSocialStatus
Indicates that one entity may hold, attain, or be associated with a particular social status in relation to another context or system.
-
D.
featuresCharacterWithStatus
Indicates that something (such as a work or scene) includes a character who has a specified status or condition.
-
E.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d616ec81908c796894f40f3015 |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.