Triple
T24223558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mick Schumacher |
E601526
|
entity |
| Predicate | reasonForRacingName |
P7885
|
FINISHED |
| Object | to avoid media attention as Michael Schumacher's son |
—
|
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: to avoid media attention as Michael Schumacher's son | Statement: [Mick Schumacher, reasonForRacingName, to avoid media attention as Michael Schumacher's son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRacingName Context triple: [Mick Schumacher, reasonForRacingName, to avoid media attention as Michael Schumacher's son]
-
A.
reasonForName
chosen
Indicates the explanation or cause behind why an entity has a particular name.
-
B.
raceName
Indicates the specific race or competition designation associated with an entity or event.
-
C.
reasonForNickname
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
D.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
E.
racingNumber
Indicates that an entity has been assigned a specific competition or race identification number used to distinguish it from other participants.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287dd148081909f02e521ad6043b1 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, midnight