Triple
T34436636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Walker |
E883974
|
entity |
| Predicate | hasCoStarInWork |
P197084
|
FINISHED |
| Object | Diana Ross |
E51575
|
NE 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: Diana Ross | Statement: [Brian Walker, hasCoStarInWork, Diana Ross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoStarInWork Context triple: [Brian Walker, hasCoStarInWork, Diana Ross]
-
A.
hasCoStarHumanCharacter
chosen
Indicates that a human character appears as a co-star alongside another character in the same work or production.
-
B.
hasPartnerInWork
Indicates that one entity collaborates professionally or is partnered with another entity in a work-related context.
-
C.
hasWorksIn
Indicates that one entity is employed by or performs their professional activities within the organization, location, or context represented by another entity.
-
D.
hasWorkUsedFor
Indicates that a particular work (e.g., document, resource, or artifact) is utilized for a specific purpose, task, or activity.
-
E.
hasCollaborationIn
Indicates that two or more entities work together or jointly participate in a specific project, context, or domain.
- F. None of above.
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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3718362d2c8190a4c4ad11a0df0cdb |
completed | June 20, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.