Triple
T27130411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Fall to Pieces |
E681547
|
entity |
| Predicate | stateOfRecording |
P167731
|
FINISHED |
| Object | Tennessee |
—
|
NE NERFINISHED |
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: Tennessee | Statement: [I Fall to Pieces, stateOfRecording, Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfRecording Context triple: [I Fall to Pieces, stateOfRecording, Tennessee]
-
A.
recordingState
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.
recordedAtState
chosen
Indicates that an event or action was officially recorded or registered within the jurisdiction of a particular state.
-
D.
isLiveRecording
Indicates that the recording was captured during a live performance or event rather than produced in a studio or through post-production.
-
E.
isReRecording
Indicates that an existing recording is being recorded again, typically to replace, update, or improve the original version.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 9:04 a.m.