Triple
T30725703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranicipitidae |
E782273
|
entity |
| Predicate | historicallyPlacedInOrder |
P198903
|
FINISHED |
| Object | Gadiformes |
—
|
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: Gadiformes | Statement: [Ranicipitidae, historicallyPlacedInOrder, Gadiformes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPlacedInOrder Context triple: [Ranicipitidae, historicallyPlacedInOrder, Gadiformes]
-
A.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
B.
chronologicallyOrders
Indicates that one entity arranges or sequences other entities according to their positions in time, from earlier to later.
-
C.
historicallyPlacedIn
Indicates that an entity was located or situated in a particular place during a specific historical period or context.
-
D.
establishedInOrder
Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
-
E.
previouslyPlacedInOrder
Indicates that an item or entity has already been included in a prior order before the current context or transaction.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
| PDg | Predicate description generation | batch_69ff136c68b481909b83d5b8a3693622 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 29, 2026, 8:36 p.m.