Triple
T29061631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oper Leipzig |
E735550
|
entity |
| Predicate | hasAdditionalFunction |
P181323
|
FINISHED |
| Object | ballet performances |
—
|
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: ballet performances | Statement: [Oper Leipzig, hasAdditionalFunction, ballet performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdditionalFunction Context triple: [Oper Leipzig, hasAdditionalFunction, ballet performances]
-
A.
hasAdditionalOperator
Indicates that an entity is associated with one or more supplementary operators beyond its primary or default operator.
-
B.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
C.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
D.
containsFunction
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
E.
hasLFunction
Indicates that an entity possesses or is associated with a specific L-function, typically representing a complex analytic function linked to its arithmetic or geometric properties.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 28, 2026, 10:15 a.m.