Triple
T19268573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izembaro |
E481854
|
entity |
| Predicate | subjectOfPlay |
P135374
|
FINISHED |
| Object | events in Westeros |
—
|
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: events in Westeros | Statement: [Izembaro, subjectOfPlay, events in Westeros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfPlay Context triple: [Izembaro, subjectOfPlay, events in Westeros]
-
A.
settingWithinPlay
Indicates that a particular setting (such as a location or environment) occurs within and is part of a specific play.
-
B.
board
Indicates that an agent gets onto or into a vehicle, vessel, or craft in order to travel or be transported.
-
C.
isTypicallyPlayed
Indicates that an activity, game, or sport is commonly engaged in or performed by a particular type of participant or group.
-
D.
starsPlay
Indicates that an entity has a leading or prominent acting role in a performance, production, or event.
-
E.
playedUnderRulesOf
Indicates that an activity or game was conducted in accordance with a specified set of rules or regulations.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb68d0c819083ba0ce680dd7d99 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:29 p.m.