Triple
T23536796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Delta |
E577619
|
entity |
| Predicate | roleAfterRacing |
P152708
|
FINISHED |
| Object | broodmare |
—
|
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: broodmare | Statement: [Royal Delta, roleAfterRacing, broodmare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAfterRacing Context triple: [Royal Delta, roleAfterRacing, broodmare]
-
A.
roleAfterConversion
Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
-
B.
roleAfterRAFClosure
Indicates that one entity holds a particular role or position in relation to another entity after the closure of the RAF (Royal Air Force) facility or organization in question.
-
C.
roleInRacingCalendar
Indicates the specific function or significance that a race or event holds within the overall racing calendar or season schedule.
-
D.
raceWon
Indicates that one participant has achieved victory in a race or competitive event over others.
-
E.
roleAfterWar
Indicates the role or position an entity assumes following the end of a war or armed conflict.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1738bc81909a7b761ddbaa1883 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:10 p.m.