Triple
T35754028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Beijing ePrix |
E1033391
|
entity |
| Predicate | gridFromPole |
P183627
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2014 Beijing ePrix, gridFromPole, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridFromPole Context triple: [2014 Beijing ePrix, gridFromPole, true]
-
A.
mapGrid
Indicates a spatial arrangement where elements are organized into a structured grid or matrix layout, typically mapping positions to coordinates or cells.
-
B.
parallelOfLatitude
Indicates that one entity is a line or circle on a sphere (typically Earth) that is at a constant latitude relative to another reference.
-
C.
planetographicLatitude
Indicates the latitude of a location on a planetary body measured in a coordinate system tied to the planet’s figure and rotation (planetographic coordinates).
-
D.
polarEquation
Indicates that a mathematical relationship is expressed as an equation in polar coordinates, relating a radius and angle rather than Cartesian coordinates.
-
E.
gridPosition
Indicates the specific location or coordinates an entity occupies within a structured grid or matrix.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1f64f1081908cc2774840684310 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a162672481909773f8383d91159a |
completed | May 3, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:06 p.m.