Triple
T3970068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sprout and the Bean |
E92306
|
entity |
| Predicate | hasLivePerformances |
P13977
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sprout and the Bean, hasLivePerformances, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivePerformances Context triple: [Sprout and the Bean, hasLivePerformances, yes]
-
A.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
-
B.
hasLiveMusic
chosen
Indicates that a place or event features live musical performances as part of its offerings.
-
C.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
-
D.
hasTouringProductions
Indicates that an entity has one or more touring versions or productions that travel to different locations.
-
E.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.