Triple
T9329773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Something's Gotta Give |
E224485
|
entity |
| Predicate | hasNotablePerformanceType |
P79011
|
FINISHED |
| Object | big band arrangement |
—
|
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: big band arrangement | Statement: [Something's Gotta Give, hasNotablePerformanceType, big band arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePerformanceType Context triple: [Something's Gotta Give, hasNotablePerformanceType, big band arrangement]
-
A.
hasNotablePerformance
Indicates that an entity has delivered a performance that is distinguished, remarkable, or otherwise noteworthy in a particular context.
-
B.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
C.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
D.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
-
E.
hasPerformanceElement
chosen
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37acbc04819092a67d7f392c74cd |
completed | April 1, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.