Triple
T28703658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McClory v. Fleming |
E729623
|
entity |
| Predicate | involvesCoCreator |
P7732
|
FINISHED |
| Object | Kevin McClory |
—
|
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: Kevin McClory | Statement: [McClory v. Fleming, involvesCoCreator, Kevin McClory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesCoCreator Context triple: [McClory v. Fleming, involvesCoCreator, Kevin McClory]
-
A.
coCreator
chosen
Indicates that two or more entities jointly created or produced something together.
-
B.
relatedWorkCreator
Indicates that the creator of one work is related (e.g., by authorship, contribution, or collaboration) to the creation of another work.
-
C.
coFounderInvolved
Indicates that an entity shares responsibility for founding another entity and is actively involved in its creation or early development.
-
D.
coCreatorOccupation
Indicates that two or more co-creators share the same occupation or professional role in relation to a creation or project.
-
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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 28, 2026, 5:44 a.m.