Triple
T416345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pride Parade |
E8000
|
entity |
| Predicate | symbolUses |
P9907
|
FINISHED |
| Object | rainbow flag |
—
|
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: rainbow flag | Statement: [Pride Parade, symbolUses, rainbow flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolUses Context triple: [Pride Parade, symbolUses, rainbow flag]
-
A.
symbolicallyUses
chosen
Indicates that one entity employs another as a symbol or representation to convey meaning, ideas, or associations rather than for its literal or practical function.
-
B.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
D.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
-
E.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
- 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.