Triple
T1923065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AlphaZero |
E40166
|
entity |
| Predicate | searchGuidance |
P6753
|
FINISHED |
| Object | policy network priors |
—
|
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: policy network priors | Statement: [AlphaZero, searchGuidance, policy network priors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchGuidance Context triple: [AlphaZero, searchGuidance, policy network priors]
-
A.
searchFeature
Indicates that an entity provides or supports functionality for searching or querying information or items.
-
B.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
-
C.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
D.
guidanceType
chosen
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
E.
defaultSearchEngine
Indicates that one entity is designated as the primary or standard search engine used by another entity (such as a user, browser, or system) for performing search queries.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb23459ac819088ded5bfac9d4aad |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.