Triple
T19313739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southside neighborhood |
E483038
|
entity |
| Predicate | timeUsePattern |
P34607
|
FINISHED |
| Object | active day and night |
—
|
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: active day and night | Statement: [Southside neighborhood, timeUsePattern, active day and night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeUsePattern Context triple: [Southside neighborhood, timeUsePattern, active day and night]
-
A.
schedulePattern
Indicates a recurring or structured timing relationship that defines when an event or action is scheduled to occur.
-
B.
workPattern
Indicates the typical schedule, structure, or arrangement according to which an entity performs its work or duties.
-
C.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
D.
timeStructure
Indicates that one entity defines, constrains, or organizes the temporal framework or schedule within which another entity exists or operates.
-
E.
usagePeak
chosen
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cfec8c8190a118b327b1418150 |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.