Triple
T13972173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Fulton Fish Market |
E336091
|
entity |
| Predicate | timeOfDayOfMainActivity |
P6019
|
FINISHED |
| Object | 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: night | Statement: [New Fulton Fish Market, timeOfDayOfMainActivity, night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDayOfMainActivity Context triple: [New Fulton Fish Market, timeOfDayOfMainActivity, night]
-
A.
hasTimeOfDay
chosen
Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
-
B.
timeOfDayEmphasized
Indicates that a particular time of day is highlighted or given special prominence in relation to an event or situation.
-
C.
timeOfDayCoverage
Indicates the specific portion or range of the day during which an activity, service, or condition is in effect or applicable.
-
D.
timeStatus
Indicates the temporal state or condition of an event or entity relative to a reference time (e.g., past, present, future, ongoing, or scheduled).
-
E.
dayPattern
Indicates the recurring schedule or configuration of days on which an event, action, or condition occurs.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e8eae40819080dd4bd25c73b6d6 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.