Triple
T24832978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMP3 |
E621388
|
entity |
| Predicate | eligibleDrivers |
P83633
|
FINISHED |
| Object | FIA Bronze drivers |
—
|
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: FIA Bronze drivers | Statement: [LMP3, eligibleDrivers, FIA Bronze drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleDrivers Context triple: [LMP3, eligibleDrivers, FIA Bronze drivers]
-
A.
allowsCupDrivers
Indicates that one entity grants permission or authorization for Cup drivers to participate in or make use of another entity.
-
B.
eligiblePersons
chosen
Indicates that certain persons meet the required conditions or criteria to qualify for a particular status, benefit, or participation.
-
C.
hasAIDrivers
Indicates that an entity possesses or is equipped with AI-based drivers that control or operate it.
-
D.
eligibleFrom
Indicates that a subject becomes or is considered eligible starting from a specified point in time or condition.
-
E.
driverRequirement
Indicates that a certain driver, qualification, or driving-related condition is required for an entity to perform or be associated with a particular role, task, or operation.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:16 a.m.