Triple
T3738361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAAB B |
E79639
|
entity |
| Predicate | hasSecurityClass |
P51148
|
FINISHED |
| Object | B |
—
|
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: B | Statement: [SAAB B, hasSecurityClass, B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityClass Context triple: [SAAB B, hasSecurityClass, B]
-
A.
hasSecurityCategory
Indicates that an entity is associated with a particular security classification or category defining its protection or access level.
-
B.
hasSecurityClause
Indicates that an agreement, contract, or document includes a provision specifying security-related requirements, protections, or safeguards.
-
C.
hasSecurityDimension
Indicates that something possesses or is associated with a particular aspect or dimension of security.
-
D.
hasSecurityRelationship
Indicates a relationship in which one entity provides, manages, or is otherwise linked to the security or protection of another entity.
-
E.
hasSecurityFunction
Indicates that an entity performs, provides, or is responsible for a security-related role, protection mechanism, or safeguarding function for another entity or system.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3e9248819098d481fe29e1c628 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc198b95481908ca6e4e875aae446 |
completed | March 8, 2026, 6:36 p.m. |
Created at: March 8, 2026, 3:34 p.m.