Triple
T30841523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unfinished |
E785521
|
entity |
| Predicate | recordingStatus |
P94748
|
FINISHED |
| Object | extensively recorded |
—
|
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: extensively recorded | Statement: [Unfinished, recordingStatus, extensively recorded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingStatus Context triple: [Unfinished, recordingStatus, extensively recorded]
-
A.
recordingState
chosen
Indicates the current status or condition of an ongoing or potential recording (e.g., whether recording is active, paused, or stopped) between entities.
-
B.
recordingMode
Indicates the method or configuration by which something is recorded, such as how data, audio, or video capture is performed.
-
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.
isOnSoundRecording
Indicates that a work, performance, or content is fixed or contained on a particular sound recording.
-
E.
isStudioRecording
Indicates that the recording was made in a controlled studio environment rather than in a live or field setting.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 29, 2026, 8:45 p.m.