Triple
T20650405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabella |
E507474
|
entity |
| Predicate | endingInPlay |
P140910
|
FINISHED |
| Object | receives a marriage proposal from the Duke |
—
|
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: receives a marriage proposal from the Duke | Statement: [Isabella, endingInPlay, receives a marriage proposal from the Duke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endingInPlay Context triple: [Isabella, endingInPlay, receives a marriage proposal from the Duke]
-
A.
hasPhaseOfPlay
Indicates a relationship where a broader game or activity includes or is associated with a specific phase or segment of play.
-
B.
settingWithinPlay
Indicates that a particular setting (such as a location or environment) occurs within and is part of a specific play.
-
C.
isBowlingEndAt
Indicates that a specific location or point on a cricket field serves as a designated bowling end for delivering the ball.
-
D.
fieldOfPlay
Indicates the spatial area or surface where an activity, event, or interaction takes place.
-
E.
clinchedInGame
Indicates that a team or player secured a decisive outcome (such as winning a series, title, or advancement) specifically in that particular game.
- F. None of above. chosen
Provenance (4 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af2133048190a6308074a3b3347e |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.