Triple
T6611778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Schumacher |
E149252
|
entity |
| Predicate | dominantEraWithTeam |
P27901
|
FINISHED |
| Object | Ferrari in early 2000s |
—
|
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: Ferrari in early 2000s | Statement: [Michael Schumacher, dominantEraWithTeam, Ferrari in early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantEraWithTeam Context triple: [Michael Schumacher, dominantEraWithTeam, Ferrari in early 2000s]
-
A.
homeTeamDuringEra
Indicates that a particular team served as the primary or official home team for an entity during a specified era or time period.
-
B.
eraOfTeamSuccess
chosen
Indicates a period during which a particular team experienced notable or sustained success.
-
C.
notableEraTeam1
Indicates that the first team is notably associated with, or representative of, a particular historical era or period.
-
D.
notableEraTeam2
Indicates that the second team is notably associated with, or prominent during, a particular historical era or period.
-
E.
teamDivisionOrEra
Indicates the specific division or historical era within which a team is categorized or competed.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cf3796d08190a26e988386089447 |
completed | March 27, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69c6acfed25481909cac74c84a9fe088 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:57 p.m.