Triple
T29937536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Muscae |
E760409
|
entity |
| Predicate | hasCompanionDetectionMethod |
P156114
|
FINISHED |
| Object | astrometric |
—
|
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: astrometric | Statement: [Delta Muscae, hasCompanionDetectionMethod, astrometric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionDetectionMethod Context triple: [Delta Muscae, hasCompanionDetectionMethod, astrometric]
-
A.
hasCompanionsDetected
Indicates that one or more accompanying entities have been identified as present alongside a given entity.
-
B.
hasModeOfDetection
chosen
Indicates that one entity is identified, measured, or observed using a specified method or technique of detection.
-
C.
supportsCompanion
Indicates that one entity provides assistance, encouragement, or backing to another entity in a companion or partner role.
-
D.
hasCompanionCore
Indicates that an entity is associated with, or accompanied by, a specific companion core.
-
E.
hasCompanionCandidate
Indicates that an entity is associated with another entity that is being considered or proposed as a potential companion.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00b8e0a5508190abc5c1e492bed12e |
completed | May 10, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_6a00b8327d048190850af317f60f0f8b |
completed | May 10, 2026, 4:54 p.m. |
Created at: April 29, 2026, 6:21 p.m.