Triple
T34637223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single Girl, Married Girl |
E889460
|
entity |
| Predicate | famouslyRecordedBy |
P67703
|
FINISHED |
| Object | Carter Family |
—
|
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: Carter Family | Statement: [Single Girl, Married Girl, famouslyRecordedBy, Carter Family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famouslyRecordedBy Context triple: [Single Girl, Married Girl, famouslyRecordedBy, Carter Family]
-
A.
mostFamouslyRecordedBy
Indicates that an item (such as a work, song, or performance) is best known or most widely associated with having been recorded by a particular entity.
-
B.
areRecordedBy
Indicates that an event, observation, or piece of information is captured or documented by a specific recording agent, device, or process.
-
C.
wasRecordedBy
Indicates that an event, observation, or piece of data was captured or documented by a specific agent, instrument, or recording process.
-
D.
famousRecord
Indicates that a particular record (such as a song, album, or performance) is widely known and recognized as notable or distinguished.
-
E.
mainlyRecordedBy
chosen
Indicates that the primary or most significant recording of something (such as a work, event, or data set) was made by a particular agent or entity.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.