Triple
T29563832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teatro de la Paz (San Luis Potosí) |
E753110
|
entity |
| Predicate | notableTypeOfEvent |
P74159
|
FINISHED |
| Object | classical music concerts |
—
|
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: classical music concerts | Statement: [Teatro de la Paz (San Luis Potosí), notableTypeOfEvent, classical music concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTypeOfEvent Context triple: [Teatro de la Paz (San Luis Potosí), notableTypeOfEvent, classical music concerts]
-
A.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
B.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
C.
notableAIEvent
Indicates that an event is recognized as significant or influential within the field of artificial intelligence.
-
D.
notableUseEvent
Indicates an event in which something is used in a way that is significant or noteworthy, distinguishing it from ordinary or routine use.
-
E.
notableCategoryType
chosen
Indicates that an entity is notably associated with or classified under a particular category type.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 5:50 p.m.