Triple
T19291882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BD+23 550 |
E482461
|
entity |
| Predicate | componentOfMultipleSystem |
P69124
|
FINISHED |
| Object | primary component |
—
|
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: primary component | Statement: [BD+23 550, componentOfMultipleSystem, primary component]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentOfMultipleSystem Context triple: [BD+23 550, componentOfMultipleSystem, primary component]
-
A.
isAComponentOf
chosen
Indicates that one entity functions as a constituent part or sub-unit of another, larger entity.
-
B.
isMultipleStarSystem
Indicates that a star system contains two or more stars gravitationally bound together, rather than a single isolated star.
-
C.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
D.
oftenPartOf
Indicates that one entity frequently occurs as a component or subset within another entity, though not necessarily always.
-
E.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc819a7881909a7afbd06d9dd3f0 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.