Triple
T25930041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wythoff Nim |
E653413
|
entity |
| Predicate | hasAnalysisMethod |
P70561
|
FINISHED |
| Object | Sprague–Grundy theory |
—
|
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: Sprague–Grundy theory | Statement: [Wythoff Nim, hasAnalysisMethod, Sprague–Grundy theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnalysisMethod Context triple: [Wythoff Nim, hasAnalysisMethod, Sprague–Grundy theory]
-
A.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
B.
hasAnalysisType
Indicates that one entity is associated with, or characterized by, a specific type or category of analysis applied to it.
-
C.
hasMethodologyFeature
chosen
Indicates that something possesses or is characterized by a particular methodological attribute, technique, or feature.
-
D.
hasMethodologyProvider
Indicates that one entity serves as the provider or source of the methodology used or applied by another entity.
-
E.
hasObservationMethod
Indicates that a particular method, technique, or procedure is used to perform or obtain an observation.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 8:36 a.m.