Triple
T14344226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Late Night with Conan O’Brien |
E355671
|
entity |
| Predicate | recordedLive |
P37189
|
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: [Late Night with Conan O’Brien, recordedLive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedLive Context triple: [Late Night with Conan O’Brien, recordedLive, true]
-
A.
recordedAsLive
chosen
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.
-
B.
notableLiveRecording
Indicates that there exists a particularly significant or well-known live recording associated with the subject.
-
C.
includesLiveRecordingFrom
Indicates that something contains or incorporates a live recording sourced from another entity.
-
D.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
E.
includesLiveRecordings
Indicates that the subject contains or features recordings captured from live performances rather than studio-produced versions.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e89ed9c8190acdb647ee618e919 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.