Triple
T25433496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domineering |
E637317
|
entity |
| Predicate | isPartOfField |
P68116
|
FINISHED |
| Object | combinatorial game theory |
—
|
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: combinatorial game theory | Statement: [Domineering, isPartOfField, combinatorial game theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfField Context triple: [Domineering, isPartOfField, combinatorial game theory]
-
A.
isFixedFieldOf
Indicates that one element is a fixed, non-variable field or attribute that belongs to and is structurally defined as part of another entity.
-
B.
inSameFieldAs
Indicates that two entities work, study, or specialize within the same professional or academic field.
-
C.
definedInField
chosen
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
-
D.
isKeyPartOf
Indicates that something functions as an essential component or crucial element within a larger whole.
-
E.
hasInfield
Indicates that an entity possesses or includes a designated infield area, typically within a larger spatial or structural context.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 1:59 p.m.