Triple
T33963699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | γ Aquarii |
E870791
|
entity |
| Predicate | isUsedAsReferencePointInNightSky |
P178132
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [γ Aquarii, isUsedAsReferencePointInNightSky, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedAsReferencePointInNightSky Context triple: [γ Aquarii, isUsedAsReferencePointInNightSky, true]
-
A.
isProminentInNightSky
Indicates that an astronomical object is easily visible and stands out in the night sky due to its brightness, size, or position.
-
B.
isForegroundStarOf
Indicates that one star appears visually in front of another star along the line of sight, occupying the foreground relative to it.
-
C.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
D.
hasDeepSkyObject
Indicates that an entity is associated with or contains a specific deep-sky astronomical object (such as a galaxy, nebula, or star cluster).
-
E.
positionInConstellation
Indicates the specific location or role an object occupies within the boundaries or structure of a given constellation.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:50 a.m.