Triple
T34585657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S^2 × R geometry |
E888036
|
entity |
| Predicate | supportsGeometricStructureOn |
P205474
|
FINISHED |
| Object | certain 3-manifolds |
—
|
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: certain 3-manifolds | Statement: [S^2 × R geometry, supportsGeometricStructureOn, certain 3-manifolds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGeometricStructureOn Context triple: [S^2 × R geometry, supportsGeometricStructureOn, certain 3-manifolds]
-
A.
supportsStructure
Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
-
B.
hasGeometry
Indicates that an entity is associated with a specific geometric representation or spatial form.
-
C.
geometricFeature
Indicates a relationship where one entity possesses or is characterized by a specific geometric property, shape, or structural feature.
-
D.
hasStructureModel
Indicates that an entity is associated with, or represented by, a specific structural model.
-
E.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2:03 a.m.