Triple
T11977837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iris germanica |
E285079
|
entity |
| Predicate | nativeStatus |
P77572
|
FINISHED |
| Object | widely naturalized in Europe |
—
|
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: widely naturalized in Europe | Statement: [Iris germanica, nativeStatus, widely naturalized in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeStatus Context triple: [Iris germanica, nativeStatus, widely naturalized in Europe]
-
A.
notNativeTo
chosen
Indicates that an entity does not originate from, or is not naturally occurring in, a specified place or environment.
-
B.
nativeOf
Indicates that an entity originates from or was born in a particular place, region, or country.
-
C.
nominalStatus
Indicates that an entity holds a particular title, label, or status in name or designation, without necessarily implying associated functions or actions.
-
D.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
E.
initialStatus
Indicates the original or starting state assigned to an entity before any changes or updates occur.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.