Triple
T6175095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acubens |
E137797
|
entity |
| Predicate | isMultipleStarSystem |
P69238
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Acubens, isMultipleStarSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultipleStarSystem Context triple: [Acubens, isMultipleStarSystem, true]
-
A.
starSystem
Indicates a relationship where an astronomical object or location belongs to, is part of, or is located within a particular star system.
-
B.
numberOfStarsWithPlanets
Indicates the count of stars that have one or more planets associated with them.
-
C.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
-
D.
isResolvedIntoIndividualStars
Indicates that an object or region, previously appearing as a single source, can be distinguished into its constituent individual stars.
-
E.
astronomicalSystem
Indicates a relationship in which multiple astronomical objects are organized into a coherent physical or dynamical system (such as a planetary system, star system, or galaxy).
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc55b5c819084482b735771c9a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.