Triple
T36574061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E0 elliptical galaxy |
E902195
|
entity |
| Predicate | hasThreeDimensionalShape |
P187005
|
FINISHED |
| Object | approximately spheroidal |
—
|
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: approximately spheroidal | Statement: [E0 elliptical galaxy, hasThreeDimensionalShape, approximately spheroidal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThreeDimensionalShape Context triple: [E0 elliptical galaxy, hasThreeDimensionalShape, approximately spheroidal]
-
A.
in3Dimensions
Indicates that something exists, occurs, or is represented within three-dimensional space.
-
B.
hasDistinctiveShape
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
C.
has3DVersion
Indicates that an entity has a corresponding three-dimensional (3D) version or representation.
-
D.
has3DModels
Indicates that an entity is associated with one or more three-dimensional (3D) digital models representing it.
-
E.
has3DGraphics
Indicates that something includes or supports three-dimensional graphical representation or rendering.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.