Triple
T19931790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9 Sagittarii |
E479070
|
entity |
| Predicate | binaryStatus |
P137887
|
FINISHED |
| Object | double-lined spectroscopic binary |
—
|
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: double-lined spectroscopic binary | Statement: [9 Sagittarii, binaryStatus, double-lined spectroscopic binary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: binaryStatus Context triple: [9 Sagittarii, binaryStatus, double-lined spectroscopic binary]
-
A.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
B.
statusInterface
Indicates that an entity serves as, or is associated with, an interface that reports or reflects its current status.
-
C.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
D.
runtimeStatus
Indicates the current operational state or condition of an entity while it is running or executing.
-
E.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a13ebc08190a583aa4c5e9f6648 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.