Triple
T36045330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 World Rally Championship |
E1042655
|
entity |
| Predicate | featuredSupportCategory |
P58189
|
FINISHED |
| Object | WRC-2 |
E315438
|
NE 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: WRC-2 | Statement: [2020 World Rally Championship, featuredSupportCategory, WRC-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredSupportCategory Context triple: [2020 World Rally Championship, featuredSupportCategory, WRC-2]
-
A.
supportsCategory
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified category.
-
B.
hasSupportCategory
chosen
Indicates that an entity is associated with a particular type or category of support it receives or provides.
-
C.
featureTypeCatalog
Indicates that an entity is associated with, or defined by, a catalog that specifies the types of features it can include or reference.
-
D.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
E.
featuresSupplication
Indicates that one entity performs or exhibits an act of earnest pleading, begging, or humble request directed toward another entity.
- F. None of above.
Provenance (4 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38cb9b762c8190a6f4734993e0d171 |
completed | June 22, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.