Triple
T7405688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Quebrada |
E170862
|
entity |
| Predicate | hasPerformanceSchedule |
P76583
|
FINISHED |
| Object | multiple daily shows |
—
|
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: multiple daily shows | Statement: [La Quebrada, hasPerformanceSchedule, multiple daily shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceSchedule Context triple: [La Quebrada, hasPerformanceSchedule, multiple daily shows]
-
A.
hasScheduleType
Indicates that an entity is associated with a particular kind or category of schedule (e.g., recurring, one-time, or specific scheduling pattern).
-
B.
hasAdministrationSchedule
Indicates that there is a defined plan or timetable specifying when and how an entity is to be administered or given.
-
C.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
D.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
E.
hasPerformanceConvention
Indicates that there is an agreed-upon set of rules, norms, or standards governing how a particular performance or activity should be carried out.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f271f1d481909a46d50b13b51a62 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f15c36d48190bc75353d3f67555a |
completed | March 27, 2026, 9:06 p.m. |
Created at: March 27, 2026, 3:10 p.m.