Triple
T5343049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J.A.R.V.I.S. |
E123986
|
entity |
| Predicate | securityClearance |
P20877
|
FINISHED |
| Object | highest level in Stark systems |
—
|
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: highest level in Stark systems | Statement: [J.A.R.V.I.S., securityClearance, highest level in Stark systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityClearance Context triple: [J.A.R.V.I.S., securityClearance, highest level in Stark systems]
-
A.
hasClearance
chosen
Indicates that one entity possesses the required authorization level or permission to access or perform actions on another entity or resource.
-
B.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
C.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
D.
governmentClassification
Indicates that an entity is assigned a specific status or category according to a government’s official classification system.
-
E.
securityStatus
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.