Triple
T24697156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germantown Festival |
E611622
|
entity |
| Predicate | typicalEntertainment |
P30079
|
FINISHED |
| Object | stage 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: stage performances | Statement: [Germantown Festival, typicalEntertainment, stage performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntertainment Context triple: [Germantown Festival, typicalEntertainment, stage performances]
-
A.
entertainmentType
chosen
Indicates the kind or category of entertainment associated with an entity or event.
-
B.
entertainmentFocus
Indicates that one entity is primarily concerned with, directed toward, or centered on providing or engaging in entertainment for another entity or context.
-
C.
shows
Indicates that one entity presents, displays, or makes another entity visible or known to an audience or observer.
-
D.
typicalCasting
Indicates that one entity is the usual or standard casting choice for portraying another entity (such as a role, character, or type).
-
E.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 3:22 a.m.