Triple
T20191181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squid Sisters |
E492980
|
entity |
| Predicate | hasLiveConcerts |
P130151
|
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: [Squid Sisters, hasLiveConcerts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveConcerts Context triple: [Squid Sisters, hasLiveConcerts, yes]
-
A.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
B.
hasLiveMusic
Indicates that a place or event features live musical performances as part of its offerings.
-
C.
hasLivePerformanceStatus
chosen
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
-
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.
hasPerformedLiveIn
Indicates that an entity has given a live performance in a specified location or venue.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad593f88190a1e534fed38b3cd7 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.