Triple
T36731384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strike Up the Band |
E907345
|
entity |
| Predicate | hasNotableCreators |
P102133
|
FINISHED |
| Object | George Gershwin |
E43641
|
NE 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: George Gershwin | Statement: [Strike Up the Band, hasNotableCreators, George Gershwin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCreators Context triple: [Strike Up the Band, hasNotableCreators, George Gershwin]
-
A.
hasNotableContentCreator
Indicates that an entity is associated with a content creator who is recognized as notable or prominent.
-
B.
hasNotableTrackCreator
Indicates that an entity has a specific creator who is notably responsible for designing or producing a track associated with it.
-
C.
hasNotableDeveloper
Indicates that an entity has a developer who is particularly prominent, influential, or otherwise notable.
-
D.
hasPrimaryCreators
chosen
Indicates that the related entities are the main or principal creators responsible for originating or producing something.
-
E.
hasNotableAwardCreatedBy
Indicates that an award received by an entity was created or established by a specific creator or organization.
- F. None of above.
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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d178e51d08190a62bba4c637535fd |
completed | June 25, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.