Triple
T416340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pride Parade |
E8000
|
entity |
| Predicate | supportsCause |
P10437
|
FINISHED |
| Object | LGBTQ+ rights |
—
|
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: LGBTQ+ rights | Statement: [Pride Parade, supportsCause, LGBTQ+ rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCause Context triple: [Pride Parade, supportsCause, LGBTQ+ rights]
-
A.
causeSupported
chosen
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
B.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
C.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
supportsTheory
Indicates that one entity provides evidence, justification, or endorsement for the validity or acceptance of another entity’s theory.
-
E.
supportsOutcome
Indicates that one entity contributes to enabling, sustaining, or improving the achievement of a particular outcome associated 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edcff4688190809d83d112ff25a5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.