Triple
T28552799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO crisis response planning |
E722931
|
entity |
| Predicate | timeSensitive |
P100973
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NATO crisis response planning, timeSensitive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSensitive Context triple: [NATO crisis response planning, timeSensitive, true]
-
A.
timeSensitivity
chosen
Indicates how strongly the relationship or action depends on, changes with, or is constrained by time.
-
B.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
C.
timeCriticalFor
Indicates that one entity must occur, be addressed, or be completed within a strict or urgent time frame in relation to another entity or condition.
-
D.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
E.
requiresTiming
Indicates that one entity’s occurrence, execution, or validity depends on being coordinated with a specific time or temporal condition related to 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6504d2594819085cc5d1276b388ac |
completed | May 2, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:43 a.m.