Triple
T13301710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mar-Keys |
E316826
|
entity |
| Predicate | roleInLabel |
P268
|
FINISHED |
| Object | house band for early Stax sessions |
—
|
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: house band for early Stax sessions | Statement: [The Mar-Keys, roleInLabel, house band for early Stax sessions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLabel Context triple: [The Mar-Keys, roleInLabel, house band for early Stax sessions]
-
A.
roleInMetadata
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
B.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
C.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
D.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
E.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:28 p.m.