Triple
T23009675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 59 Cygni |
E572871
|
entity |
| Predicate | massFunction |
P150638
|
FINISHED |
| Object | derived from radial‑velocity curve |
—
|
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: derived from radial‑velocity curve | Statement: [59 Cygni, massFunction, derived from radial‑velocity curve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massFunction Context triple: [59 Cygni, massFunction, derived from radial‑velocity curve]
-
A.
massSupport
Indicates that a large number of individuals collectively endorse, approve of, or back a particular entity, action, or position.
-
B.
massForm
Indicates that an entity takes shape or comes into existence as a mass or aggregate form.
-
C.
massFront
Indicates that one entity is positioned directly in front of or facing the front side of another entity in terms of mass or physical arrangement.
-
D.
massContribution
Indicates that an entity contributes some or all of its mass to another entity or system.
-
E.
massProperty
Indicates that one entity has a mass-related physical property or characteristic associated with it.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18359f5548190b15a139eb09e30a0 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:51 p.m.