Triple
T5808603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suresnes American Cemetery |
E128809
|
entity |
| Predicate | hasVisitingHours |
P17011
|
FINISHED |
| Object | daily except certain holidays |
—
|
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: daily except certain holidays | Statement: [Suresnes American Cemetery, hasVisitingHours, daily except certain holidays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitingHours Context triple: [Suresnes American Cemetery, hasVisitingHours, daily except certain holidays]
-
A.
hoursOfOperation
Indicates the time periods during which a place or service is open and available for use.
-
B.
openingHoursCharacteristic
chosen
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
C.
has24HourOperations
Indicates that an entity operates continuously for 24 hours a day without closing.
-
D.
hasAfterHoursSession
Indicates that an entity conducts or participates in a session that takes place outside of regular or standard operating hours.
-
E.
canVisit
Indicates that one entity is permitted or able to go to or access another entity or location.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1867a481909a7ea3331dbb04ce |
completed | March 22, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.