Triple
T18229426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6 Hours of Bahrain |
E436502
|
entity |
| Predicate | entryList |
P124974
|
FINISHED |
| Object | factory teams and privateer teams |
—
|
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: factory teams and privateer teams | Statement: [6 Hours of Bahrain, entryList, factory teams and privateer teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryList Context triple: [6 Hours of Bahrain, entryList, factory teams and privateer teams]
-
A.
entryFor
Indicates that one entity serves as the specific record, representation, or listing corresponding to another entity.
-
B.
typicalEntryList
chosen
Indicates a relationship where an entity is associated with a standard or representative list of entries that are commonly or normally linked to it.
-
C.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
-
D.
entryDistribution
Indicates how entries are allocated, spread, or assigned across a set of targets or categories.
-
E.
inscriptionList
Indicates that there is a list or collection of inscriptions associated with an entity.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b1b2108190a5585bbfaf2d295b |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.