Triple
T30157573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equation |
E766563
|
entity |
| Predicate | hasSiblingCollaborationWith |
P69164
|
FINISHED |
| Object | Ronald Burrell |
—
|
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: Ronald Burrell | Statement: [Equation, hasSiblingCollaborationWith, Ronald Burrell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiblingCollaborationWith Context triple: [Equation, hasSiblingCollaborationWith, Ronald Burrell]
-
A.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
B.
hasSubsequentCollaboration
Indicates that one entity engages in a follow-up or later collaboration with another entity after an initial joint activity or partnership.
-
C.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
D.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
E.
hasArtistSiblingCollaboration
chosen
Indicates that two artist siblings have worked together on a shared artistic project or collaboration.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 7:21 p.m.