Triple
T18771906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menkib |
E459033
|
entity |
| Predicate | opticalCompanionType |
P69911
|
FINISHED |
| Object | line-of-sight companion, not gravitationally bound |
—
|
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: line-of-sight companion, not gravitationally bound | Statement: [Menkib, opticalCompanionType, line-of-sight companion, not gravitationally bound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opticalCompanionType Context triple: [Menkib, opticalCompanionType, line-of-sight companion, not gravitationally bound]
-
A.
usesOpticsType
Indicates that one entity employs or is characterized by a specific type of optical system or technology.
-
B.
hasCompanionStar
Indicates that an astronomical object is gravitationally bound to and forms a system with another star.
-
C.
lensType
Indicates the specific kind or category of lens associated with or used by an entity.
-
D.
visualCompanion
chosen
Indicates that one entity serves as a visual counterpart, partner, or accompanying element to another in a visual context.
-
E.
notableCompanionType
Indicates that one entity is a prominent or significant type of companion or associate 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_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. |
Created at: April 10, 2026, 11:52 a.m.