Triple
T15282728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shah |
E365310
|
entity |
| Predicate | usedInChessTerm |
P101388
|
FINISHED |
| Object | "shah" meaning check in Persian chess terminology |
—
|
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: "shah" meaning check in Persian chess terminology | Statement: [Shah, usedInChessTerm, "shah" meaning check in Persian chess terminology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInChessTerm Context triple: [Shah, usedInChessTerm, "shah" meaning check in Persian chess terminology]
-
A.
usedInTournamentAbbreviations
Indicates that a particular abbreviation is used to represent something within the context of a tournament.
-
B.
inChess
chosen
Indicates that the relationship or action occurs within the context, rules, or domain of the game of chess.
-
C.
kingIsInviolable
Indicates that the king is protected from harm, violation, or infringement, often implying legal or moral immunity from certain actions.
-
D.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
E.
usedInPlayByPlayFor
Indicates that something (such as data, terminology, or a resource) is utilized within the context of a play-by-play account or commentary.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e51f82081909f63d14b589d5587 |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:15 a.m.