Triple
T9133852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Brother No. 1 |
E219152
|
entity |
| Predicate | bearerKnownFor |
P15030
|
FINISHED |
| Object | pioneering funk music |
—
|
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: pioneering funk music | Statement: [Soul Brother No. 1, bearerKnownFor, pioneering funk music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerKnownFor Context triple: [Soul Brother No. 1, bearerKnownFor, pioneering funk music]
-
A.
underlyingKnownFor
Indicates that one entity is fundamentally or primarily recognized as the basis or main reason for another entity’s notability or fame.
-
B.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
C.
laterKnownFor
Indicates that an entity became recognized or notable for something at a later time than the context or event currently being referred to.
-
D.
followersKnownAs
Indicates that the followers of an entity are referred to by a particular name or label.
-
E.
alsoKnownFor
chosen
Indicates that an entity is additionally recognized or noted for another work, role, achievement, or characteristic beyond its primary association.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8dccecc81908d8fc641c419ca6a |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.