Triple
T33234036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernie Wise |
E850777
|
entity |
| Predicate | partnerInDoubleActWith |
P76526
|
FINISHED |
| Object | Eric Morecambe |
—
|
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: Eric Morecambe | Statement: [Ernie Wise, partnerInDoubleActWith, Eric Morecambe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInDoubleActWith Context triple: [Ernie Wise, partnerInDoubleActWith, Eric Morecambe]
-
A.
partnerInActWith
Indicates that two or more entities jointly participate as partners in carrying out the same act or action.
-
B.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
-
C.
partnerInSeries
Indicates that two entities are co-participants or collaborators within the same series, jointly contributing to or appearing in that ongoing sequence.
-
D.
laterPartnerInPracticeWith
Indicates that one entity became a partner in professional practice with another entity at a later point in time.
-
E.
partnerInComedyDuo
chosen
Indicates that two entities are partners together in a comedy duo act or performance team.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:31 a.m.