Triple
T27133748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Souslin operation |
E681625
|
entity |
| Predicate | typicalIndexSet |
P149159
|
FINISHED |
| Object | ω^ω |
—
|
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: ω^ω | Statement: [Souslin operation, typicalIndexSet, ω^ω]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIndexSet Context triple: [Souslin operation, typicalIndexSet, ω^ω]
-
A.
indexSet
Indicates a relationship where one entity serves as the index or indexing structure used to organize, reference, or access elements of another set or collection.
-
B.
requiresIndicesType
Indicates that one entity depends on or mandates a specific type or format of indices from another entity in order to function or be valid.
-
C.
typicalActiveSubset
Indicates that one set is a representative or characteristic active portion of a larger set, capturing the typical elements or behavior of that larger set.
-
D.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
E.
hasIndexSet
chosen
Indicates that something is associated with, defined over, or organized according to a particular set of indices.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: April 27, 2026, 9:05 a.m.