Triple
T19981495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Frederick |
E493824
|
entity |
| Predicate | actionAtEndOfPlay |
P38927
|
FINISHED |
| Object | restores the dukedom to Duke Senior |
—
|
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: restores the dukedom to Duke Senior | Statement: [Duke Frederick, actionAtEndOfPlay, restores the dukedom to Duke Senior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionAtEndOfPlay Context triple: [Duke Frederick, actionAtEndOfPlay, restores the dukedom to Duke Senior]
-
A.
opponentActionEnded
Indicates that an opposing party’s action or move has been completed or has come to an end.
-
B.
scoreAfterPlay
Indicates the numerical score that results immediately after a specific play or action has been completed.
-
C.
finalSceneAction
chosen
Indicates the action or event that occurs in the concluding or final scene of a narrative or sequence.
-
D.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
E.
disappearsFromPlayAfter
Indicates that an entity is removed from active play and no longer participates in the game after a specified event or condition occurs.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d13a8a88190bf5f4f697793f4c9 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:28 p.m.