Triple
T13291329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silberpfeile |
E316565
|
entity |
| Predicate | dominanceIn |
P2547
|
FINISHED |
| Object | European Championship motor racing |
—
|
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: European Championship motor racing | Statement: [Silberpfeile, dominanceIn, European Championship motor racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominanceIn Context triple: [Silberpfeile, dominanceIn, European Championship motor racing]
-
A.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
B.
imposedDominanceOf
Indicates that one entity has forcibly asserted control, authority, or superiority over another, typically without the latter’s consent.
-
C.
dominantOn
chosen
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
D.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
E.
confirmedDominanceOf
Indicates that one entity has been verified or officially recognized as having dominance or superiority over another 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.