Triple
T14237296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Ford |
E352914
|
entity |
| Predicate | publiclyDiscussed |
P82614
|
FINISHED |
| Object | her breast cancer diagnosis |
—
|
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: her breast cancer diagnosis | Statement: [Elizabeth Ford, publiclyDiscussed, her breast cancer diagnosis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyDiscussed Context triple: [Elizabeth Ford, publiclyDiscussed, her breast cancer diagnosis]
-
A.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
-
B.
discussionPublic
chosen
Indicates that a discussion is accessible to the general public rather than being restricted or private.
-
C.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
D.
discussed
Indicates that one entity talked about, examined, or debated a topic, issue, or other entity with someone else.
-
E.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62422e28819089e7115052a28c96 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.