Triple
T20714295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Direct |
E509127
|
entity |
| Predicate | customerServiceAvailability |
P10068
|
FINISHED |
| Object | 24 hours a day |
—
|
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 hours a day | Statement: [First Direct, customerServiceAvailability, 24 hours a day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerServiceAvailability Context triple: [First Direct, customerServiceAvailability, 24 hours a day]
-
A.
hoursOfOperation
chosen
Indicates the time periods during which a place or service is open and available for use.
-
B.
serviceAvailability
Indicates whether a particular service is accessible and operational for use during a given time or under specified conditions.
-
C.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
D.
availableOnlineAt
Indicates that something can be accessed or obtained via a specified online source or location.
-
E.
serviceOpenedBetween
Indicates that a service has been initiated or made available during the time interval between two specified points or events.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d001788190a524a17347f9de67 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.