Triple
T28550756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sale and Pelletier |
E722878
|
entity |
| Predicate | formedPartnership |
P27289
|
FINISHED |
| Object | late 1990s |
—
|
LITERAL FINISHED |
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: late 1990s | Statement: [Sale and Pelletier, formedPartnership, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedPartnership Context triple: [Sale and Pelletier, formedPartnership, late 1990s]
-
A.
formedAsPartnershipBetween
chosen
Indicates that something was created or established through a formal partnership between two or more entities.
-
B.
formedOpeningPartnershipWith
Indicates that two entities started an event or sequence together by jointly forming the initial partnership or collaboration.
-
C.
endedPartnershipWith
Indicates that a previously existing partnership or collaborative relationship between two entities has been terminated.
-
D.
formerPartner
Indicates that one entity was previously in a romantic or partnership relationship with another entity, but that relationship has since ended.
-
E.
formerJointVentureWith
Indicates that two entities were previously engaged together in a joint venture relationship that has since ended.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: April 28, 2026, 3:42 a.m.