Triple
T29958204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Full Madness Pass |
E760966
|
entity |
| Predicate | usableDuring |
P4341
|
FINISHED |
| Object | festival opening hours |
—
|
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: festival opening hours | Statement: [Full Madness Pass, usableDuring, festival opening hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usableDuring Context triple: [Full Madness Pass, usableDuring, festival opening hours]
-
A.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
B.
usableAs
Indicates that one entity can function in place of or serve the purpose of another entity.
-
C.
ownedDuring
Indicates that one entity possessed or held ownership of another entity for some or all of a specified time interval.
-
D.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
E.
usedBetween
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6783c19d081909aa0691853c370de |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:28 p.m.