Triple
T13509343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lent Bumps |
E321094
|
entity |
| Predicate | startOrderDeterminedBy |
P110040
|
FINISHED |
| Object | previous year's finishing order |
—
|
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: previous year's finishing order | Statement: [Lent Bumps, startOrderDeterminedBy, previous year's finishing order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOrderDeterminedBy Context triple: [Lent Bumps, startOrderDeterminedBy, previous year's finishing order]
-
A.
establishedWithOrder
Indicates that something is created, initiated, or set up in accordance with a specified order or sequence.
-
B.
entersOrderThrough
Indicates that one party places or submits an order by means of, or via the involvement of, another party or system.
-
C.
establishedForOrder
Indicates that something has been created or set up specifically to serve, support, or fulfill a particular order.
-
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.
orderFoundedBy
Indicates that a particular order or organization was established or created by a specific person or entity.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf85a74081909eb08751fc55ce8f |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaee128d88190b097be17fdd2f92b |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.