Triple
T28855806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoplestigmataceae |
E728730
|
entity |
| Predicate | previousOrderAssignment |
P123953
|
FINISHED |
| Object | Boraginales |
—
|
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: Boraginales | Statement: [Hoplestigmataceae, previousOrderAssignment, Boraginales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousOrderAssignment Context triple: [Hoplestigmataceae, previousOrderAssignment, Boraginales]
-
A.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
B.
formerOrder
chosen
Indicates that one entity previously held a particular order, position, or status in relation to another entity, but no longer does so.
-
C.
originalOrder
Indicates that the entities are arranged or referenced according to their initial, unaltered sequence or configuration.
-
D.
previouslyPlacedInOrder
Indicates that an item or entity has already been included in a prior order before the current context or transaction.
-
E.
distributionOrder
Indicates the sequence or arrangement in which items or resources are distributed among recipients or locations.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 28, 2026, 6:45 a.m.