Triple
T26428481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maureen Johnson |
E664434
|
entity |
| Predicate | currentPartner |
P1136
|
FINISHED |
| Object | Joanne Jefferson |
—
|
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: Joanne Jefferson | Statement: [Maureen Johnson, currentPartner, Joanne Jefferson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentPartner Context triple: [Maureen Johnson, currentPartner, Joanne Jefferson]
-
A.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
B.
selectedPartner
Indicates that one entity has been chosen or designated as the partner of another entity.
-
C.
primaryPartners
Indicates that the entities are each other’s main or most significant partners in a relationship, typically implying priority or exclusivity over other partnerships.
-
D.
coalitionPartnerWith
Indicates that two entities are formally aligned in a cooperative coalition, sharing goals or actions as partners within that coalition.
-
E.
hasPartner
chosen
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 26, 2026, 11:47 p.m.