Triple
T4792116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gresham Butte |
E106625
|
entity |
| Predicate | threatHistory |
P14802
|
FINISHED |
| Object | past development proposals |
—
|
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: past development proposals | Statement: [Gresham Butte, threatHistory, past development proposals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatHistory Context triple: [Gresham Butte, threatHistory, past development proposals]
-
A.
historicalThreat
chosen
Indicates that one entity posed a significant threat to another in the past, but is not necessarily a current or ongoing danger.
-
B.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
D.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
-
E.
securityHistory
Indicates a record of past security-related events, states, or changes associated with an 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.