Triple
T65837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLRW cosmological models |
E1311
|
entity |
| Predicate | spatialSections |
P3120
|
FINISHED |
| Object | 3-sphere |
—
|
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: 3-sphere | Statement: [FLRW cosmological models, spatialSections, 3-sphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spatialSections Context triple: [FLRW cosmological models, spatialSections, 3-sphere]
-
A.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
C.
section7Provides
Indicates that Section 7 serves as the source or provider of something (such as rights, obligations, benefits, or content) to another party or element.
-
D.
physiographicDivisionOf
Indicates that one geographic area is a sub-region or component within the larger physiographic division of another area.
-
E.
hasSectionCount
Indicates that an entity is associated with a specific number of sections it contains or comprises.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.