Triple
T28943474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 51 Pegasi b |
E730517
|
entity |
| Predicate | atmosphericCompositionEvidence |
P10615
|
FINISHED |
| Object | water vapor |
—
|
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: water vapor | Statement: [51 Pegasi b, atmosphericCompositionEvidence, water vapor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atmosphericCompositionEvidence Context triple: [51 Pegasi b, atmosphericCompositionEvidence, water vapor]
-
A.
secondaryAtmosphericConstituent
chosen
Indicates that an entity has a specified substance as a non-primary (secondary) component of its atmosphere.
-
B.
hasMainAtmosphericComponent
Indicates that one entity has another entity as the primary constituent of its atmosphere.
-
C.
hasAtmosphericFeature
Indicates that one entity possesses or exhibits a particular feature or characteristic of its atmosphere.
-
D.
capturesAtmosphereOf
Indicates that one entity successfully conveys or reflects the overall mood, tone, or ambiance characteristic of another entity.
-
E.
usesAtmosphereOf
Indicates that one entity makes use of or operates within the atmospheric conditions or composition associated with another entity.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 8:38 a.m.