Triple
T31592380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lichtenvoorde |
E806133
|
entity |
| Predicate | flowerParadeType |
P171998
|
FINISHED |
| Object | parade with dahlia-covered floats |
—
|
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: parade with dahlia-covered floats | Statement: [Lichtenvoorde, flowerParadeType, parade with dahlia-covered floats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowerParadeType Context triple: [Lichtenvoorde, flowerParadeType, parade with dahlia-covered floats]
-
A.
flowerType
Indicates the specific kind or category of flower associated with an entity.
-
B.
flowerUse
Indicates how a flower is used or purposed in a particular context (e.g., decorative, medicinal, culinary, or symbolic use).
-
C.
flowerFunction
Indicates the biological or practical role that a flower serves, such as reproduction, attraction of pollinators, or ornamental use.
-
D.
flowerClusterType
Indicates the specific arrangement or grouping pattern in which individual flowers are clustered together.
-
E.
flowerPosition
Indicates the spatial location or arrangement of a flower relative to a reference object or coordinate system.
- F. None of above. chosen
Provenance (4 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:28 p.m.