Triple
T29600892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American flora section |
E754440
|
entity |
| Predicate | isThemedBy |
P20708
|
FINISHED |
| Object | geographical origin of plants |
—
|
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: geographical origin of plants | Statement: [North American flora section, isThemedBy, geographical origin of plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isThemedBy Context triple: [North American flora section, isThemedBy, geographical origin of plants]
-
A.
isThemedTo
Indicates that one entity is designed, styled, or conceptually based around the subject, motif, or theme represented by another entity.
-
B.
usesThemeBy
Indicates that one entity incorporates, applies, or is based on a theme that was created, defined, or provided by another entity.
-
C.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
D.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
E.
themedAs
chosen
Indicates that something is characterized, styled, or organized according to a particular theme or motif.
- 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_69f66dbae46881909b6543de2bd2f273 |
completed | May 2, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:22 p.m.