Triple
T19666674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Treasure |
E472217
|
entity |
| Predicate | containsLiveRecordings |
P104299
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [A Treasure, containsLiveRecordings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLiveRecordings Context triple: [A Treasure, containsLiveRecordings, true]
-
A.
includesLiveRecordings
chosen
Indicates that the subject contains or features recordings captured from live performances rather than studio-produced versions.
-
B.
includesLiveRecordingFrom
Indicates that something contains or incorporates a live recording sourced from another entity.
-
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.
isFrequentlyRecordedLive
Indicates that the subject is often captured or documented in live recordings, such as live performances, broadcasts, or real-time sessions.
-
E.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641694e448190bc734c07ae2df024 |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.