Triple
T15842408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sauber Motorsport |
E384130
|
entity |
| Predicate | enteredF1In |
P82780
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Sauber Motorsport, enteredF1In, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredF1In Context triple: [Sauber Motorsport, enteredF1In, 1993]
-
A.
enteredFormulaOne
chosen
Indicates that an entity began competing in Formula One racing, marking its entry into the Formula One championship.
-
B.
heldFIAEntry
Indicates that an entity possessed or maintained an official FIA (Fédération Internationale de l'Automobile) entry status for a competition or event.
-
C.
enteredNRLIn
Indicates that an entity began participating in the NRL (National Rugby League) competition in a specified season or year.
-
D.
enteredIntoForceIn
Indicates that an agreement, law, or treaty became legally effective or operative in a specified place or jurisdiction.
-
E.
enteredIntoForce
Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e88ff08190a1035269e8fdaa6a |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005434ed88190baf11c169da3cf29 |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.