Triple
T5187328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA-95 air defense system |
E117063
|
entity |
| Predicate | systemComponents |
P840
|
FINISHED |
| Object | launcher vehicle |
—
|
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: launcher vehicle | Statement: [CA-95 air defense system, systemComponents, launcher vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemComponents Context triple: [CA-95 air defense system, systemComponents, launcher vehicle]
-
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.
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.
-
D.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
E.
partOfSystem
chosen
Indicates that one entity functions as a component or subsystem within the structure or organization of 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c3e9e08190848be4208b72f310 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.