Triple
T7187078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Movember |
E167598
|
entity |
| Predicate | supportsIssue |
P1853
|
FINISHED |
| Object | early detection of prostate cancer |
—
|
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: early detection of prostate cancer | Statement: [Movember, supportsIssue, early detection of prostate cancer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIssue Context triple: [Movember, supportsIssue, early detection of prostate cancer]
-
A.
supportsProject
Indicates that one entity provides assistance, resources, or endorsement to help another entity’s project succeed.
-
B.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
C.
support
chosen
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
D.
supportsAspect
Indicates that one entity provides backing, justification, or reinforcement for a particular aspect, feature, or component of another entity.
-
E.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.