Triple
T27658931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prix of Portland |
E697066
|
entity |
| Predicate | returnedToSchedule |
P126990
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Grand Prix of Portland, returnedToSchedule, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToSchedule Context triple: [Grand Prix of Portland, returnedToSchedule, 2018]
-
A.
returnedToCalendar
chosen
Indicates that an entity has been restored or moved back to a calendar after previously being removed, hidden, or moved elsewhere.
-
B.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
C.
returnedToServiceIn
Indicates that an entity resumed active use or operation at a particular time or in a particular context after having been out of service.
-
D.
rescheduledTo
Indicates that an event or action has been moved from its original time to a new specified time.
-
E.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 2:35 p.m.