Triple
T31549990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulip Festival in Morges |
E804971
|
entity |
| Predicate | hasPrimaryPlant |
P7837
|
FINISHED |
| Object | tulip |
—
|
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 | Statement: [Tulip Festival in Morges, hasPrimaryPlant, tulip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryPlant Context triple: [Tulip Festival in Morges, hasPrimaryPlant, tulip]
-
A.
hasMajorPlant
Indicates that one entity possesses or hosts a primary or most significant plant facility or installation in relation to another entity.
-
B.
isMajorPlant
Indicates that a plant holds primary or dominant importance within a given context, such as size, influence, or role.
-
C.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
D.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
-
E.
hasPlantSymbol
chosen
Indicates that an entity is associated with or represented by a particular plant as its symbolic emblem or sign.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a007338002081908cb6340d65ff86d5 |
completed | May 10, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a0072a137ac8190a7debeb28e738e03 |
completed | May 10, 2026, 11:57 a.m. |
Created at: April 30, 2026, 10:10 p.m.