Triple
T29768248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamaeleon |
E753974
|
entity |
| Predicate | alphaDesignation |
P24821
|
FINISHED |
| Object | Alpha Chamaeleontis |
—
|
NE NERFINISHED |
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: Alpha Chamaeleontis | Statement: [Chamaeleon, alphaDesignation, Alpha Chamaeleontis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alphaDesignation Context triple: [Chamaeleon, alphaDesignation, Alpha Chamaeleontis]
-
A.
alternateDesignation
Indicates that one entity serves as an alternative name, label, or identifier for another entity.
-
B.
AVADesignation
Indicates that an entity has been assigned a specific AVA (American Viticultural Area) designation, linking it to a formally recognized wine-growing region.
-
C.
bayerDesignation
chosen
Indicates the assignment of a star’s Bayer designation, linking a star to its specific Greek-letter-plus-constellation label used in astronomy.
-
D.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
E.
bdDesignation
Indicates that one entity is formally assigned or designated as having a particular role, status, or classification in relation to 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6745f8354819085a81de5c32dd49e |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:39 p.m.