Triple
T5349913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chameleon |
E124149
|
entity |
| Predicate | hasLivePerformanceRecordings |
P45543
|
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: [Chameleon, hasLivePerformanceRecordings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivePerformanceRecordings Context triple: [Chameleon, hasLivePerformanceRecordings, 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.
hasPerformedLiveIn
Indicates that an entity has given a live performance in a specified location or venue.
-
C.
notableLiveRecording
chosen
Indicates that there exists a particularly significant or well-known live recording associated with the subject.
-
D.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
-
E.
recordedAsLive
Indicates that an audio or video performance was captured in real time before an audience or in a live setting, rather than produced or edited in a studio environment.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd860fe4048190846a933d0e1b9386 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.