Triple
T18771802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | o Persei |
E459031
|
entity |
| Predicate | binaryCompanionType |
P133481
|
FINISHED |
| Object | early-type star |
—
|
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: early-type star | Statement: [o Persei, binaryCompanionType, early-type star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: binaryCompanionType Context triple: [o Persei, binaryCompanionType, early-type star]
-
A.
binaryType
Indicates that something is classified as a binary type, typically distinguishing between two mutually exclusive categories or values.
-
B.
notableCompanionType
Indicates that one entity is a prominent or significant type of companion or associate in relation to another entity.
-
C.
includesCompanion
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
D.
hasCompanionStar
Indicates that an astronomical object is gravitationally bound to and forms a system with another star.
-
E.
numericCompanionCode
Indicates that one entity is associated with another through a specific numeric companion code used to link or reference them.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:52 a.m.