Triple
T27886052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio in the South |
E705225
|
entity |
| Predicate | plannedCollaborator |
P54367
|
FINISHED |
| Object | Paul Gauguin |
—
|
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: Paul Gauguin | Statement: [Studio in the South, plannedCollaborator, Paul Gauguin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedCollaborator Context triple: [Studio in the South, plannedCollaborator, Paul Gauguin]
-
A.
primaryCollaborator
Indicates that one entity serves as the main or most significant partner working jointly with another entity on a shared activity, project, or goal.
-
B.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
C.
plannedWith
chosen
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
collaboratorsInclude
Indicates that a specified collaborator is included among the collaborators associated with an entity or activity.
-
E.
collaboratorName
Indicates that the predicate specifies the name of a person or entity who collaborates with another in some shared activity or project.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 6:33 p.m.