Triple
T2576860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Top |
E56995
|
entity |
| Predicate | hasSubsequentRecording |
P28321
|
FINISHED |
| Object | Lynn Anderson version |
—
|
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: Lynn Anderson version | Statement: [Rocky Top, hasSubsequentRecording, Lynn Anderson version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsequentRecording Context triple: [Rocky Top, hasSubsequentRecording, Lynn Anderson version]
-
A.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
B.
laterRecordedIn
chosen
Indicates that the referenced information or event was documented or captured at a later time in the specified source or record.
-
C.
recordingExists
Indicates that there is an existing recorded instance (such as audio, video, or other media) associated with the specified entities or event.
-
D.
hasRecordingContract
Indicates that an entity is formally bound by an agreement to produce recordings for another entity, typically a record label or similar organization.
-
E.
hasSubsequentAward
Indicates that an entity has received an additional award that follows a previous award in time or sequence.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a73a508190bf12e889a5d4bbf3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.