Triple
T30679370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotton Plant, Arkansas |
E781008
|
entity |
| Predicate | hasNotableMusicHeritage |
P202064
|
FINISHED |
| Object | gospel |
—
|
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: gospel | Statement: [Cotton Plant, Arkansas, hasNotableMusicHeritage, gospel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMusicHeritage Context triple: [Cotton Plant, Arkansas, hasNotableMusicHeritage, gospel]
-
A.
hasNotableMusicWork
Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
-
B.
hasNotableNamesakeContribution
Indicates that an entity has made a significant contribution specifically related to or inspired by its notable namesake.
-
C.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
D.
hasNotableHistoricalAssociation
Indicates that there is a significant connection between an entity and an important historical event, figure, period, or development.
-
E.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
- F. None of above. chosen
Provenance (4 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
| PDg | Predicate description generation | batch_6a004b69d8788190965dcf3653ac88a9 |
completed | May 10, 2026, 9:10 a.m. |
Created at: April 29, 2026, 8:32 p.m.