Triple
T179329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakutani fixed-point theorem |
E3648
|
entity |
| Predicate | involvesStructure |
P1256
|
FINISHED |
| Object | Euclidean space |
—
|
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: Euclidean space | Statement: [Kakutani fixed-point theorem, involvesStructure, Euclidean space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesStructure Context triple: [Kakutani fixed-point theorem, involvesStructure, Euclidean space]
-
A.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
B.
involvesInstitution
Indicates that an action, event, or relationship includes or is associated with an institution as a participating party.
-
C.
involvesWorkers
Indicates that an event, process, or situation includes workers as active participants or affected parties.
-
D.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
E.
hasOrganizationalStructure
Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and operates.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a25900709c8190a65e778936be5dd5 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.