Triple
T28206031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie Fisher |
E717023
|
entity |
| Predicate | creativePartnerOf |
P106180
|
FINISHED |
| Object | Alex Fletcher |
—
|
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: Alex Fletcher | Statement: [Sophie Fisher, creativePartnerOf, Alex Fletcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativePartnerOf Context triple: [Sophie Fisher, creativePartnerOf, Alex Fletcher]
-
A.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
B.
partnerInProductionCompanyWith
Indicates that two entities are business partners together in operating or owning the same production company.
-
C.
partnerInWorkOf
chosen
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
D.
partnerOfArtist
Indicates a relationship where one entity is the romantic or life partner of an artist.
-
E.
partnerInArtWorldWith
Indicates that two entities collaborate or are closely associated as partners within the art world context, such as in creation, curation, representation, or promotion of art.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 10:35 p.m.