Triple
T1092665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Maid's Revenge |
E24199
|
entity |
| Predicate | hasCourtlySetting |
P3538
|
FINISHED |
| Object | Spanish nobility |
—
|
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: Spanish nobility | Statement: [The Maid's Revenge, hasCourtlySetting, Spanish nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtlySetting Context triple: [The Maid's Revenge, hasCourtlySetting, Spanish nobility]
-
A.
hasDressCode
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
B.
hasCourtyard
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
C.
hasRoyalHousehold
Indicates that an entity possesses or is associated with a specific royal household as its official domestic or courtly establishment.
-
D.
hasSetting
chosen
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
E.
servesAtThePleasureOf
Indicates that one entity holds a position or role that can be terminated at any time by another entity, typically at the discretion or will of that other entity.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99bd06c8190bce1d77b0337b07c |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b743175481908f3967e589717c55 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.