Triple
T36574060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E0 elliptical galaxy |
E902195
|
entity |
| Predicate | hasMorphologicalCode |
P199993
|
FINISHED |
| Object | E0 |
—
|
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: E0 | Statement: [E0 elliptical galaxy, hasMorphologicalCode, E0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMorphologicalCode Context triple: [E0 elliptical galaxy, hasMorphologicalCode, E0]
-
A.
hasMorphologicalExpression
Indicates that a particular concept, feature, or grammatical category is realized or marked through a specific morphological form or pattern.
-
B.
hasMorphologicalState
Indicates that an entity possesses or is characterized by a particular morphological condition, form, or structural state.
-
C.
hasMorphologicalPattern
Indicates that one entity exhibits or follows a specific morphological pattern defined or associated with another entity.
-
D.
hasMorphosyntax
Indicates a relationship where an entity is associated with, characterized by, or analyzed in terms of its morphological and syntactic structure.
-
E.
hasMorphologicalType
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
- 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_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
| PDg | Predicate description generation | batch_69ff691e86d0819099fdb5eca5a95632 |
completed | May 9, 2026, 5:04 p.m. |
Created at: May 3, 2026, 4:11 p.m.