Triple
T17340932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banach–Mazur game |
E421063
|
entity |
| Predicate | hasMoveType |
P127090
|
FINISHED |
| Object | choice of nonempty open set |
—
|
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: choice of nonempty open set | Statement: [Banach–Mazur game, hasMoveType, choice of nonempty open set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoveType Context triple: [Banach–Mazur game, hasMoveType, choice of nonempty open set]
-
A.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
B.
hasMovementVariant
Indicates that one movement is an alternative or variant form of another movement.
-
C.
includesMovementType
Indicates that one entity encompasses or contains a specific type or category of movement associated with another entity.
-
D.
hasMovementOrder
Indicates that one entity is assigned or associated with a specific directive or sequence for movement or relocation.
-
E.
hasAnimationType
Indicates the specific style or method of animation applied to an entity or its visual content.
- F. None of above. chosen
Provenance (4 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a15f6488190ad7d489e7391ab12 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.