Triple
T619016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernard Hinault |
E14468
|
entity |
| Predicate | ridingStyle |
P15815
|
FINISHED |
| Object | aggressive |
—
|
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: aggressive | Statement: [Bernard Hinault, ridingStyle, aggressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ridingStyle Context triple: [Bernard Hinault, ridingStyle, aggressive]
-
A.
ridingSpecialty
chosen
Indicates that one entity has a particular area of expertise or focus related to riding (e.g., a specific riding style, discipline, or type).
-
B.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
-
C.
flightStyle
Indicates the characteristic manner or pattern in which an entity performs or exhibits flight.
-
D.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
E.
mobilityCharacteristic
Indicates a relationship where an entity is described or classified in terms of its movement or transportation-related properties, such as how, how well, or under what conditions it can move or be moved.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e25956c8190a1eed87002548658 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfe9bc081909a01b4b3b48f03b7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.