Triple
T30337992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leela Chess Zero |
E771672
|
entity |
| Predicate | usesSearchAlgorithm |
P55275
|
FINISHED |
| Object | Monte Carlo tree search |
—
|
NE NERFINISHED |
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: Monte Carlo tree search | Statement: [Leela Chess Zero, usesSearchAlgorithm, Monte Carlo tree search]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSearchAlgorithm Context triple: [Leela Chess Zero, usesSearchAlgorithm, Monte Carlo tree search]
-
A.
usedToSearchFor
Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve another entity.
-
B.
usesSearchTechnologyFrom
Indicates that one entity employs or relies on the search technology developed or provided by another entity.
-
C.
usesExplorationMethod
chosen
Indicates that one entity employs or applies a particular exploration method as part of its process or behavior.
-
D.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
E.
usesScanningMethod
Indicates that an entity performs or carries out an action by employing a specific scanning method.
- 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_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 7:54 p.m.