Triple
T36719314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudy Reyes |
E907003
|
entity |
| Predicate | authorOfSourceMaterialCollaboratedWith |
P60681
|
FINISHED |
| Object | Evan Wright |
—
|
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: Evan Wright | Statement: [Rudy Reyes, authorOfSourceMaterialCollaboratedWith, Evan Wright]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOfSourceMaterialCollaboratedWith Context triple: [Rudy Reyes, authorOfSourceMaterialCollaboratedWith, Evan Wright]
-
A.
basedOnAuthorCollaboratedWith
Indicates that one entity is derived from, influenced by, or created using work that was produced through a collaboration between the specified author and another contributor.
-
B.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
-
C.
hasCollaboratedIn
chosen
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
D.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
E.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:12 p.m.