Triple
T12496206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Least Concern |
E298690
|
entity |
| Predicate | positionInScale |
P61184
|
FINISHED |
| Object | lowest threat category for evaluated species |
—
|
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: lowest threat category for evaluated species | Statement: [Least Concern, positionInScale, lowest threat category for evaluated species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInScale Context triple: [Least Concern, positionInScale, lowest threat category for evaluated species]
-
A.
positionInTimeScale
Indicates the specific point or interval an event or state occupies within a defined temporal scale or timeline.
-
B.
scalePosition
chosen
Indicates the relative location or index of an element within a defined scale or ordered measurement framework.
-
C.
positionInMass
Indicates that an entity occupies a specific location or role within a larger undifferentiated group, collection, or mass.
-
D.
positionInRange
Indicates that an entity’s position lies within a specified numerical or spatial range.
-
E.
positionInFrame
Indicates the spatial location or coordinates of an entity within a specific frame or reference image.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:57 p.m.