Triple
T27142303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Heather County |
E681845
|
entity |
| Predicate | hasFloralAssociation |
P104578
|
FINISHED |
| Object | heather |
—
|
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: heather | Statement: [The Heather County, hasFloralAssociation, heather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloralAssociation Context triple: [The Heather County, hasFloralAssociation, heather]
-
A.
hasFloralFeature
Indicates that an entity possesses a specific floral characteristic, structure, or attribute.
-
B.
hasFlowerColor
Indicates that an entity (typically a plant or flower) possesses a specific flower color.
-
C.
hasMainFloralSymbol
chosen
Indicates that an entity is associated with a primary or most representative floral symbol.
-
D.
belongsToFloralKingdom
Indicates that something is classified as part of the floral kingdom, typically encompassing plants and related botanical life forms.
-
E.
sharesFloralElementsWith
Indicates that two entities have flowers or floral structures with similar or overlapping elements, such as shapes, patterns, or component parts.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 9:10 a.m.