Triple
T18763333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAM-4 |
E458829
|
entity |
| Predicate | systemComponent |
P840
|
FINISHED |
| Object | missile launcher |
—
|
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: missile launcher | Statement: [SAM-4, systemComponent, missile launcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemComponent Context triple: [SAM-4, systemComponent, missile launcher]
-
A.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
B.
systemEntry
Indicates that an entity is being recorded, registered, or introduced into a particular system or structured environment.
-
C.
partOfSystem
chosen
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
D.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
E.
systemBoard
Indicates a relationship where a system is associated with, mounted on, or implemented via a particular main circuit board (motherboard) that hosts its core components.
- 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_69e58d80a954819083946dafc0c7af05 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.