Triple
T31970208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanker |
E816290
|
entity |
| Predicate | appliesToGuidanceType |
P197665
|
FINISHED |
| Object | inertial guidance |
—
|
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: inertial guidance | Statement: [Spanker, appliesToGuidanceType, inertial guidance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToGuidanceType Context triple: [Spanker, appliesToGuidanceType, inertial guidance]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
appliesToServiceType
Indicates that something is relevant or applicable specifically to a particular type or category of service.
-
C.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
D.
appliesToSegmentType
Indicates that a rule, condition, or operation is specifically associated with and relevant to a particular type of segment.
-
E.
appliesToProductType
Indicates that something (such as a rule, offer, or condition) is relevant or applicable specifically to a certain type or category of product.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: May 1, 2026, 12:10 a.m.