Triple
T30338069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houdini (chess engine) |
E771673
|
entity |
| Predicate | hasInterfaceCompatibility |
P12981
|
FINISHED |
| Object | ChessBase GUIs |
—
|
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: ChessBase GUIs | Statement: [Houdini (chess engine), hasInterfaceCompatibility, ChessBase GUIs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterfaceCompatibility Context triple: [Houdini (chess engine), hasInterfaceCompatibility, ChessBase GUIs]
-
A.
hasInterface
chosen
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
B.
checksCompatibilityWith
Indicates that one entity evaluates whether it is compatible or can function harmoniously with another entity.
-
C.
hasBinaryCompatibilityWith
Indicates that two entities can operate or interact correctly at the binary level without requiring recompilation or modification.
-
D.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
E.
hasCompatibilityMode
Indicates that one entity operates under a special mode or setting designed to maintain compatibility with another entity or with an earlier version.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: April 29, 2026, 7:54 p.m.