Triple
T6057752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire on the Mountain |
E134956
|
entity |
| Predicate | isFrequentlyRecordedLive |
P68020
|
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: [Fire on the Mountain, isFrequentlyRecordedLive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyRecordedLive Context triple: [Fire on the Mountain, isFrequentlyRecordedLive, true]
-
A.
isFrequentlyRecorded
Indicates that an entity is captured or documented many times within a given dataset, medium, or context.
-
B.
isLiveRecording
Indicates that the recording was captured during a live performance or event rather than produced in a studio or through post-production.
-
C.
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.
-
D.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
-
E.
isOftenRecordedWith
Indicates that one entity is frequently documented, captured, or logged at the same time as another entity.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570d00e88190b2d8d596e40378d9 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:09 p.m.