Triple
T27652293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardly Strictly Bluegrass |
E696893
|
entity |
| Predicate | mainPerformanceArea |
P89589
|
FINISHED |
| Object | Hellman Hollow |
—
|
NE NERFINISHED |
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: Hellman Hollow | Statement: [Hardly Strictly Bluegrass, mainPerformanceArea, Hellman Hollow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformanceArea Context triple: [Hardly Strictly Bluegrass, mainPerformanceArea, Hellman Hollow]
-
A.
performanceArea
chosen
Indicates the area or space in which a performance, show, or event takes place.
-
B.
mainPerformanceSpaceOf
Indicates that one space or venue serves as the primary location where performances or events for another entity (such as an organization, production, or festival) are held.
-
C.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
D.
mainlyPerformed
Indicates that an action or activity is carried out primarily or predominantly by a particular entity compared to others.
-
E.
performanceBasis
Indicates that one entity’s performance is evaluated, determined, or justified on the basis of another specified factor, standard, or reference.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 2:32 p.m.