Triple
T30468220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Little Italy |
E775210
|
entity |
| Predicate | isLiveOrStudio |
P142087
|
FINISHED |
| Object | live performance recording |
—
|
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: live performance recording | Statement: [Princess of Little Italy, isLiveOrStudio, live performance recording]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLiveOrStudio Context triple: [Princess of Little Italy, isLiveOrStudio, live performance recording]
-
A.
liveOrStudio
chosen
Indicates whether something (typically a performance or recording) was done live or in a studio setting.
-
B.
isLive
Indicates that an entity is currently broadcasting or occurring in real time, as opposed to being pre-recorded or inactive.
-
C.
isLiveRecording
Indicates that the recording was captured during a live performance or event rather than produced in a studio or through post-production.
-
D.
isStudioRecording
Indicates that the recording was made in a controlled studio environment rather than in a live or field setting.
-
E.
isLiveVersion
Indicates that one entity is the current, active, or publicly available version of another entity.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f4d5c48190b3d9430466d3e3ff |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:11 p.m.