Triple
T23981522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engler system of plant classification |
E604519
|
entity |
| Predicate | placesFirst |
P154121
|
FINISHED |
| Object | simplest thalloid 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: simplest thalloid plants | Statement: [Engler system of plant classification, placesFirst, simplest thalloid plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placesFirst Context triple: [Engler system of plant classification, placesFirst, simplest thalloid plants]
-
A.
firstLocation
Indicates the initial or primary place where an entity is situated, originates, or where an event or relationship begins.
-
B.
places
Indicates that one entity assigns, positions, or puts another entity into a specific location, role, or context.
-
C.
firstSeriesLocation
Indicates the location where a series first took place, was set, or was initially released.
-
D.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
E.
placesInQuestion
Indicates that an entity is located within, or occurs in, the spatial or contextual scope defined by a given question.
- F. None of above. chosen
Provenance (4 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2be350c8190a0f8937094f4a902 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:28 p.m.