Triple
T9515231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torpids |
E229507
|
entity |
| Predicate | raceStructure |
P88494
|
FINISHED |
| Object | head of the river positions |
—
|
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: head of the river positions | Statement: [Torpids, raceStructure, head of the river positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceStructure Context triple: [Torpids, raceStructure, head of the river positions]
-
A.
raceTypeDetail
Indicates the specific category or classification of a race, providing detailed information about the type of race involved in the relationship.
-
B.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
C.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
D.
stageRaceType
Indicates the specific category or format of a multi-stage race within a broader competition or event.
-
E.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986d5af08190a001c5a5ff647d4d |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:58 p.m.