Triple
T20736393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oude Kwaremont |
E509719
|
entity |
| Predicate | oftenDecisiveFor |
P23903
|
FINISHED |
| Object | selection of race favourites |
—
|
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: selection of race favourites | Statement: [Oude Kwaremont, oftenDecisiveFor, selection of race favourites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDecisiveFor Context triple: [Oude Kwaremont, oftenDecisiveFor, selection of race favourites]
-
A.
decisiveFor
chosen
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
B.
decisive
Indicates that one entity makes a conclusive choice or determination that resolves a situation or outcome between entities.
-
C.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
D.
decisiveness
Indicates the degree to which an entity consistently makes timely, firm choices without excessive hesitation or reversal.
-
E.
decisiveFeature
Indicates that one feature or characteristic plays a determining role in deciding an outcome or distinguishing between alternatives.
- 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20a02d48190bba22d1bdbeb370d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:31 p.m.