Triple
T36871168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seifert fibered space |
E911225
|
entity |
| Predicate | supportsGeometry |
P203
|
FINISHED |
| Object | S^3-geometry (in some cases) |
—
|
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: S^3-geometry (in some cases) | Statement: [Seifert fibered space, supportsGeometry, S^3-geometry (in some cases)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGeometry Context triple: [Seifert fibered space, supportsGeometry, S^3-geometry (in some cases)]
-
A.
supports3DTransforms
Indicates that one entity provides or is compatible with three-dimensional transform capabilities for another entity or within a given context.
-
B.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
C.
supportsSRID
Indicates that one entity provides compatibility with, recognition of, or operational support for a specified Spatial Reference System Identifier (SRID) associated with another entity.
-
D.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
supportsBoundingBoxes
Indicates that an entity is capable of handling, displaying, or otherwise working with bounding box representations for objects or regions.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.