Triple
T27254789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusternik–Schnirelmann category |
E687582
|
entity |
| Predicate | definesFunctionOn |
P4464
|
FINISHED |
| Object | topological spaces |
—
|
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: topological spaces | Statement: [Lusternik–Schnirelmann category, definesFunctionOn, topological spaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesFunctionOn Context triple: [Lusternik–Schnirelmann category, definesFunctionOn, topological spaces]
-
A.
definesFunAs
Indicates that one entity specifies or establishes the meaning, behavior, or implementation of a function for another entity.
-
B.
definedOn
chosen
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
C.
definesFunctioningOf
Indicates that one entity specifies or determines how another entity operates or functions.
-
D.
definesOperationOn
Indicates that one entity specifies or establishes the operation that is applied to another entity.
-
E.
exposesFunction
Indicates that one entity makes a function available for use or access by another entity or 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 10:48 a.m.