Triple
T27565424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Park lake (Bidhannagar) |
E695886
|
entity |
| Predicate | hasTimeOfPeakUse |
P34607
|
FINISHED |
| Object | evenings |
—
|
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: evenings | Statement: [Central Park lake (Bidhannagar), hasTimeOfPeakUse, evenings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeOfPeakUse Context triple: [Central Park lake (Bidhannagar), hasTimeOfPeakUse, evenings]
-
A.
usagePeak
chosen
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
B.
isOnPeak
Indicates that one entity is located at, or positioned on, the highest point or summit of another entity.
-
C.
hasPeakHourService
Indicates that a service operates or is available during designated peak or high-demand hours.
-
D.
hasPeakHourFunction
Indicates that something performs a specific role or behavior during peak hours of activity or usage.
-
E.
hasOffPeakUsage
Indicates that an entity exhibits or is associated with usage occurring during designated off-peak times rather than standard peak periods.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 1:41 p.m.