Triple
T35948568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nylandtia |
E1039653
|
entity |
| Predicate | hasFormerSpecies |
P32513
|
FINISHED |
| Object | Nylandtia spinosa |
—
|
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: Nylandtia spinosa | Statement: [Nylandtia, hasFormerSpecies, Nylandtia spinosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerSpecies Context triple: [Nylandtia, hasFormerSpecies, Nylandtia spinosa]
-
A.
formerSpecies
chosen
Indicates that an entity was previously classified as a particular species but no longer holds that species status.
-
B.
evolvedWith
Indicates that two or more entities have undergone evolutionary change in mutual influence or parallel over time.
-
C.
evolvedIn
Indicates that an entity originated or developed within a specified environment, context, or location over evolutionary time.
-
D.
evolvedUnder
Indicates that one entity developed or changed over time while being influenced or shaped by specific conditions, factors, or an environment represented by the other entity.
-
E.
originSpecies
Indicates that one entity is the original or source species from which another entity is derived, evolved, or produced.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:07 p.m.