Triple
T25822421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guarded Threat Level |
E650437
|
entity |
| Predicate | associatedSystemStatus |
P32380
|
FINISHED |
| Object | Homeland Security Advisory System active |
—
|
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: Homeland Security Advisory System active | Statement: [Guarded Threat Level, associatedSystemStatus, Homeland Security Advisory System active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSystemStatus Context triple: [Guarded Threat Level, associatedSystemStatus, Homeland Security Advisory System active]
-
A.
associatedSystem
chosen
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
B.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
C.
statusInSystem7
Indicates that an entity holds a particular status or state within the context of system 7.
-
D.
associatedState
Indicates that one entity is linked or connected to a particular state, condition, or status of another entity.
-
E.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 22, 2026, 7:30 a.m.