Triple
T9104721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilac Parade |
E218448
|
entity |
| Predicate | hasVisualElement |
P43274
|
FINISHED |
| Object | floral decorations |
—
|
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: floral decorations | Statement: [Lilac Parade, hasVisualElement, floral decorations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisualElement Context triple: [Lilac Parade, hasVisualElement, floral decorations]
-
A.
hasVisualIndicator
Indicates that an entity is associated with some form of visual cue or marker that signals its status, condition, or presence.
-
B.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
C.
hasVisibility
Indicates that one entity can perceive, view, or access another entity or its information under certain conditions.
-
D.
hasControlElement
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
E.
hasExhibitElement
chosen
Indicates that something (such as an exhibit or display) includes or is composed of a particular element or component.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca5714d048190a633caaaa707ac3b |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.