Triple
T11196205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble (Martian crater) |
E264926
|
entity |
| Predicate | isAstronomicalObject |
P97798
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hubble (Martian crater), isAstronomicalObject, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAstronomicalObject Context triple: [Hubble (Martian crater), isAstronomicalObject, yes]
-
A.
observedAstronomicalBody
Indicates that an entity has observed, detected, or recorded data about a particular astronomical body.
-
B.
astronomicalType
Indicates the classification relationship that specifies what kind of astronomical object or phenomenon something is (e.g., star, galaxy, planet).
-
C.
hasDeepSkyObject
Indicates that an entity is associated with or contains a specific deep-sky astronomical object (such as a galaxy, nebula, or star cluster).
-
D.
DeAstronomicaIs
Indicates that something is identified as or classified as "De Astronomica" (e.g., belonging to or being the work/text known as De Astronomica).
-
E.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c082fc8190866c574f698b59ef |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.