Triple
T2924329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salamanca Market |
E78806
|
entity |
| Predicate | openingTime |
P43960
|
FINISHED |
| Object | 08:30 |
—
|
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: 08:30 | Statement: [Salamanca Market, openingTime, 08:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingTime Context triple: [Salamanca Market, openingTime, 08:30]
-
A.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
B.
roofOpeningTime
Indicates the time at which a roof (typically movable or retractable) is opened.
-
C.
closingTime
Indicates the specific time at which a place, service, or activity stops operating or becomes unavailable.
-
D.
openPitClosedIn
Indicates that an open-pit mine or excavation has been closed, decommissioned, or otherwise taken out of active use at a specified time or under specified conditions.
-
E.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
- F. None of above. chosen
Provenance (4 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f520208190a4dc43372004555f |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:55 p.m.