Triple
T8078710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Carrera Cup Asia |
E188559
|
entity |
| Predicate | digitalCoverage |
P80373
|
FINISHED |
| Object | online streaming platforms |
—
|
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: online streaming platforms | Statement: [Porsche Carrera Cup Asia, digitalCoverage, online streaming platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalCoverage Context triple: [Porsche Carrera Cup Asia, digitalCoverage, online streaming platforms]
-
A.
dataCoverage
Indicates the extent or proportion of relevant data that is included, captured, or represented within a given dataset or system.
-
B.
networkCoverage
Indicates the extent to which a network’s signal or service is available across a given area or to specific entities.
-
C.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
D.
mapCoverage
Indicates the extent or area that is represented, covered, or included by a particular map.
-
E.
hasFrequencyCoverage
Indicates that one entity provides, supports, or is applicable across a specified range or set of frequencies associated with another entity.
- F. None of above. chosen
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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a2b64c8190ae2b3414b4f840e4 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:28 p.m.