Triple
T754286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadttheater Fürth |
E15518
|
entity |
| Predicate | categoryOfPeopleServed |
P19115
|
FINISHED |
| Object | local community of Fürth |
—
|
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: local community of Fürth | Statement: [Stadttheater Fürth, categoryOfPeopleServed, local community of Fürth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryOfPeopleServed Context triple: [Stadttheater Fürth, categoryOfPeopleServed, local community of Fürth]
-
A.
servesMostly
Indicates that one entity primarily functions to serve, support, or cater to another entity, more than to any other.
-
B.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
-
C.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
D.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
E.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64ecadc8190a82e25444e7abba6 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a501c4cc81908de6d63e3d4f60d7 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a5bed20c81909ecc28bf42594e72 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.