Triple
T23657119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Valley 1919 (with interruptions) |
E584333
|
entity |
| Predicate | hasInterruptedUse |
P6409
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Valley 1919 (with interruptions), hasInterruptedUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterruptedUse Context triple: [The Valley 1919 (with interruptions), hasInterruptedUse, yes]
-
A.
wasInterruptedBy
Indicates that an ongoing event, action, or process was stopped or disrupted by another event, action, or agent.
-
B.
hasInterruptController
Indicates that an entity is associated with or includes an interrupt controller responsible for managing hardware or software interrupts.
-
C.
hasHistoricalInterruptions
chosen
Indicates that the continuity of an event, process, or relationship has been broken by one or more distinct interruptions over time.
-
D.
supportsInterrupt
Indicates that one entity is capable of handling or accommodating an interruption initiated by another entity.
-
E.
hasPresentUse
Indicates that an entity is currently being used or serving a particular function at the present time.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35c257c81909f7004c0a35be4e3 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.