Triple
T19932213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Ophiuchi |
E479081
|
entity |
| Predicate | hasVariableStatus |
P137889
|
FINISHED |
| Object | non-variable |
—
|
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: non-variable | Statement: [Alpha Ophiuchi, hasVariableStatus, non-variable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariableStatus Context triple: [Alpha Ophiuchi, hasVariableStatus, non-variable]
-
A.
hasExistenceStatus
Indicates that an entity is associated with a particular state of existence, such as being current, historical, planned, or no longer existing.
-
B.
hasModelStatus
Indicates that an entity is assigned a particular model-related state or condition, such as its current phase, validity, or operational status within a modeling context.
-
C.
hasVolunteerStatus
Indicates that an entity holds a particular volunteer-related status or role within a specified context.
-
D.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
E.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
- 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_69e65a14a2348190b41f8e320fe661d6 |
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.