Triple
T13426238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rallye Deutschland |
E313488
|
entity |
| Predicate | notableStageFeature |
P61000
|
FINISHED |
| Object | concrete tank tracks |
—
|
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: concrete tank tracks | Statement: [Rallye Deutschland, notableStageFeature, concrete tank tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStageFeature Context triple: [Rallye Deutschland, notableStageFeature, concrete tank tracks]
-
A.
notableStage
Indicates that an entity is recognized as an important or distinguished stage or phase in relation to another entity or process.
-
B.
notableFeatureOn
chosen
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
C.
notableBroadcastFeature
Indicates that something has a distinctive or noteworthy characteristic related to its broadcast or transmission.
-
D.
notableStand
Indicates that an entity is particularly well-known or distinguished for a specific stance, position, or viewpoint.
-
E.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed066408190a416880affd8416e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.