Triple
T4701468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari |
E104281
|
entity |
| Predicate | isMostSuccessfulTeamIn |
P2706
|
FINISHED |
| Object | Formula One history by constructors’ titles |
—
|
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: Formula One history by constructors’ titles | Statement: [Ferrari, isMostSuccessfulTeamIn, Formula One history by constructors’ titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMostSuccessfulTeamIn Context triple: [Ferrari, isMostSuccessfulTeamIn, Formula One history by constructors’ titles]
-
A.
isOneOfMostSuccessfulTeamsIn
Indicates that a team ranks among the most successful teams within a specified group, context, or location.
-
B.
mostAwardsHolderTeam
Indicates the team that holds the highest number of awards within a given set or competition.
-
C.
eraOfTeamSuccess
Indicates a period during which a particular team experienced notable or sustained success.
-
D.
winningTeam
Indicates which team is the victor in a given competition, game, or contest.
-
E.
mostSuccessfulClub
chosen
Indicates that one club holds the highest level of success (e.g., by titles, achievements, or performance) compared to all other clubs in the given context.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.