Triple
T35479194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanamaker Grand Court Organ |
E1025421
|
entity |
| Predicate | hasSpecialConcerts |
P197465
|
FINISHED |
| Object | annual Christmas 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: annual Christmas concerts | Statement: [Wanamaker Grand Court Organ, hasSpecialConcerts, annual Christmas concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialConcerts Context triple: [Wanamaker Grand Court Organ, hasSpecialConcerts, annual Christmas concerts]
-
A.
performedInConcertTours
Indicates that an entity (typically an artist or performer) took part in one or more concert tours.
-
B.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
-
C.
notableConcert
Indicates that a concert event is recognized as particularly significant, memorable, or influential in some notable way.
-
D.
hasSpecialSong
Indicates that one entity possesses or is associated with a particular song that is unique, distinctive, or specially designated for it.
-
E.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69fe9208ed708190980fb5061b22ae49 |
completed | May 9, 2026, 1:46 a.m. |
Created at: May 3, 2026, 4:04 p.m.