Triple
T28585469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MECA |
E723491
|
entity |
| Predicate | managesEventType |
P134123
|
FINISHED |
| Object | 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: concerts | Statement: [MECA, managesEventType, concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesEventType Context triple: [MECA, managesEventType, concerts]
-
A.
typeOfEventManaged
chosen
Indicates that an entity is responsible for organizing, overseeing, or handling a specific category or kind of event.
-
B.
regulatesEvent
Indicates that one entity controls, influences, or modulates the occurrence, timing, or intensity of an event.
-
C.
accessibleForEventType
Indicates that something can be used, reached, or is available in the context of a specified type or category of event.
-
D.
mainEventManager
Indicates that an entity serves as the primary controller or coordinator responsible for managing a central event or set of events in relation to another entity.
-
E.
eventManagement
Indicates the organization, coordination, and oversight of all activities and resources involved in planning and executing an event.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 4:17 a.m.