Triple
T2706262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fine Guidance Sensor |
E59347
|
entity |
| Predicate | guidingMode |
P6753
|
FINISHED |
| Object | locks onto single guide 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: locks onto single guide star | Statement: [Fine Guidance Sensor, guidingMode, locks onto single guide star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidingMode Context triple: [Fine Guidance Sensor, guidingMode, locks onto single guide star]
-
A.
guidedBy
Indicates that an entity’s actions, decisions, or movement are directed, advised, or led by another entity.
-
B.
guidanceType
chosen
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
C.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
D.
guidanceControl
Indicates that one entity directs, manages, or influences the behavior or decisions of another through guidance or control.
-
E.
primaryGuidanceSystem
Indicates that one entity functions as the main or principal guidance or navigation system for 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda725f24819090e8d936b3d2d5bc |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.