Triple
T16106905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 61st Street–Woodside |
E390760
|
entity |
| Predicate | hasTimePeriodService |
P99305
|
FINISHED |
| Object | 24/7 |
—
|
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: 24/7 | Statement: [61st Street–Woodside, hasTimePeriodService, 24/7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodService Context triple: [61st Street–Woodside, hasTimePeriodService, 24/7]
-
A.
hasServiceTime
chosen
Indicates that an entity is associated with a specific duration or schedule during which a service is provided.
-
B.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
-
C.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
D.
hasTimeOptions
Indicates that an entity is associated with one or more selectable time choices or configurations.
-
E.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6e55c08190b77f344e4e8c42ad |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.