Triple
T5674919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Small Paraklesis |
E125061
|
entity |
| Predicate | typicalTimeOfUse |
P6833
|
FINISHED |
| Object | times of need |
—
|
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: times of need | Statement: [Small Paraklesis, typicalTimeOfUse, times of need]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTimeOfUse Context triple: [Small Paraklesis, typicalTimeOfUse, times of need]
-
A.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
B.
electricityUse
Indicates the amount or pattern of electrical energy consumed by an entity during a specified period or activity.
-
C.
electrificationUsedBetween
Indicates that an electrification system or method is applied or present along the segment or connection between two entities.
-
D.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
E.
peakHours
Indicates that an action, event, or condition occurs during the busiest or most heavily trafficked time period.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.