Triple
T30660397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Don't Mind |
E780508
|
entity |
| Predicate | hasLivePerformanceBorough |
P193128
|
FINISHED |
| Object | Harlem |
—
|
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: Harlem | Statement: [I Don't Mind, hasLivePerformanceBorough, Harlem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivePerformanceBorough Context triple: [I Don't Mind, hasLivePerformanceBorough, Harlem]
-
A.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
B.
hasLivePerformanceStatus
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
-
C.
hasLivePerformanceOrigin
Indicates that something originates from, or is derived from, a live performance event.
-
D.
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.
-
E.
hasLivePerformanceReputation
Indicates that an entity is recognized or characterized by a particular reputation regarding the quality or nature of its live performances.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:31 p.m.