Triple
T22999100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altair |
E572585
|
entity |
| Predicate | hemisphereProminence |
P74677
|
FINISHED |
| Object | northern summer sky |
—
|
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: northern summer sky | Statement: [Altair, hemisphereProminence, northern summer sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hemisphereProminence Context triple: [Altair, hemisphereProminence, northern summer sky]
-
A.
prominenceFeature
Indicates that one entity serves as a notable or distinguishing feature that contributes significantly to the prominence or recognizability of another entity.
-
B.
prominence
Indicates that an entity stands out in importance, visibility, or influence relative to others within a given context.
-
C.
prominenceType
chosen
Indicates the specific kind or category of prominence or notability associated with an entity in a given context.
-
D.
prominenceUnit
Indicates the unit of measurement used to quantify the degree or level of prominence in a given context.
-
E.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f54ce88190930530958e2a1830 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.