Triple
T8993112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmo shogi engine |
E214836
|
entity |
| Predicate | supportsRuleSet |
P6249
|
FINISHED |
| Object | standard Japanese shogi rules |
—
|
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: standard Japanese shogi rules | Statement: [Elmo shogi engine, supportsRuleSet, standard Japanese shogi rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRuleSet Context triple: [Elmo shogi engine, supportsRuleSet, standard Japanese shogi rules]
-
A.
supportRules
Indicates that one entity provides justification, backing, or validation for the rules or constraints defined by another entity.
-
B.
usesRulesFrom
chosen
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
C.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
D.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
E.
supportedRegime
Indicates that an entity provided assistance, endorsement, or backing to a particular political regime or government in power.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6876583081909d936dc3c3152587 |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.