Triple
T28189720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Originators |
E716264
|
entity |
| Predicate | hasArtistCollaborationType |
P83689
|
FINISHED |
| Object | posse cut |
—
|
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: posse cut | Statement: [The Originators, hasArtistCollaborationType, posse cut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtistCollaborationType Context triple: [The Originators, hasArtistCollaborationType, posse cut]
-
A.
hasArtistSiblingCollaboration
Indicates that two artist siblings have worked together on a shared artistic project or collaboration.
-
B.
hasNotableCollaborationType
chosen
Indicates a specific kind or category of significant collaborative relationship that exists between entities.
-
C.
musicalCollaborator
Indicates a relationship where two or more entities work together in creating, performing, or producing music.
-
D.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
E.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 10:25 p.m.