Triple
T8568165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crying |
E202859
|
entity |
| Predicate | recordingLabelLocation |
P45205
|
FINISHED |
| Object | Nashville-based Monument Records |
—
|
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: Nashville-based Monument Records | Statement: [Crying, recordingLabelLocation, Nashville-based Monument Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingLabelLocation Context triple: [Crying, recordingLabelLocation, Nashville-based Monument Records]
-
A.
recordLabelLocation
chosen
Indicates the geographic place where a record label is based or operates from.
-
B.
recordLabelForNotableRecording
Indicates that a record label is responsible for producing, releasing, or prominently associated with a particular notable recording.
-
C.
placeOfRecording
Indicates the location where an audio, video, or other recording was made.
-
D.
recordLabelForHitRecording
Indicates that a record label is responsible for producing or releasing a particular hit recording.
-
E.
hasRecordingLabel
Indicates that an entity (such as an artist or release) is associated with a particular recording label that publishes or distributes its music.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d5d4ac8190a4d74c88b872d0b7 |
completed | March 31, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.