Triple
T35567895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Wit Me |
E1027827
|
entity |
| Predicate | collaborationUnderName |
P45539
|
FINISHED |
| Object | 7 Days of Funk |
—
|
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: 7 Days of Funk | Statement: [High Wit Me, collaborationUnderName, 7 Days of Funk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationUnderName Context triple: [High Wit Me, collaborationUnderName, 7 Days of Funk]
-
A.
collaborationName
Indicates the designated name or title assigned to a specific collaboration between entities.
-
B.
collaboratorName
chosen
Indicates that the predicate specifies the name of a person or entity who collaborates with another in some shared activity or project.
-
C.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
D.
usesCollaboration
Indicates that one entity employs or relies on collaborative methods, tools, or partnerships with another entity to achieve a shared goal or perform an activity.
-
E.
collaborationAt
Indicates that two or more entities are working together or jointly engaged in an activity, project, or context at a specific place, organization, or event.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.