Triple
T10461302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIM-7 Sea Sparrow |
E246679
|
entity |
| Predicate | guidanceUpdate |
P6753
|
FINISHED |
| Object | mid-course guidance via ship radar |
—
|
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: mid-course guidance via ship radar | Statement: [RIM-7 Sea Sparrow, guidanceUpdate, mid-course guidance via ship radar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidanceUpdate Context triple: [RIM-7 Sea Sparrow, guidanceUpdate, mid-course guidance via ship radar]
-
A.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
B.
guidanceType
chosen
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
C.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
D.
guidedBy
Indicates that an entity’s actions, decisions, or movement are directed, advised, or led by another entity.
-
E.
conditionForGuidance
Indicates that one entity serves as a prerequisite or determining factor for another entity to provide guidance or direction.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50883b62c819082711b8c9fd968e3 |
completed | April 7, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:19 p.m.