Triple
T29600891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American flora section |
E754440
|
entity |
| Predicate | regionOfFloralOrigin |
P150308
|
FINISHED |
| Object | North America |
—
|
NE NERFINISHED |
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: North America | Statement: [North American flora section, regionOfFloralOrigin, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfFloralOrigin Context triple: [North American flora section, regionOfFloralOrigin, North America]
-
A.
hasFloralRegion
Indicates that one entity possesses or is associated with a specific floral region as a characteristic or component.
-
B.
cultivarOrigin
Indicates that a particular plant cultivar was originally developed, bred, or derived from a specified source location, population, or lineage.
-
C.
hasRegionalFlower
Indicates that a region is associated with a specific flower designated as its symbolic or representative flower.
-
D.
hasFloristicRegion
chosen
Indicates that an entity is located in, associated with, or belongs to a particular floristic (plant-distribution) region.
-
E.
speciesOrigin
Indicates the place, environment, or source from which a species originally arose or evolved.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 28, 2026, 6:22 p.m.