Triple
T36045637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Leclerc |
E1042662
|
entity |
| Predicate | contractExtendedWith |
P147628
|
FINISHED |
| Object | Scuderia Ferrari |
—
|
NE NERFINISHED |
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: Scuderia Ferrari | Statement: [Charles Leclerc, contractExtendedWith, Scuderia Ferrari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractExtendedWith Context triple: [Charles Leclerc, contractExtendedWith, Scuderia Ferrari]
-
A.
contractExtensionAnnounced
chosen
Indicates that an official announcement has been made that an existing contract will be extended beyond its original terms or end date.
-
B.
contractFeature
Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
-
C.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
-
D.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
-
E.
extendedOn
Indicates that one entity continues, prolongs, or expands the duration, scope, or effect of another entity beyond its original limit.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 3, 2026, 4:07 p.m.