Triple
T1143103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aalsmeer flower market stalls (part of Bloemenmarkt) |
E23499
|
entity |
| Predicate | typicalProduct |
P7216
|
FINISHED |
| Object | tulip bulbs |
—
|
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: tulip bulbs | Statement: [Aalsmeer flower market stalls (part of Bloemenmarkt), typicalProduct, tulip bulbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProduct Context triple: [Aalsmeer flower market stalls (part of Bloemenmarkt), typicalProduct, tulip bulbs]
-
A.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
B.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
C.
primaryProduct
chosen
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4e93d48190b9fea886bf61aad7 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.