Triple
T23193890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IndyCar Series street circuit races |
E579821
|
entity |
| Predicate | pitStopRequirement |
P44365
|
FINISHED |
| Object | multiple pit stops |
—
|
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: multiple pit stops | Statement: [IndyCar Series street circuit races, pitStopRequirement, multiple pit stops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pitStopRequirement Context triple: [IndyCar Series street circuit races, pitStopRequirement, multiple pit stops]
-
A.
pitStopRules
Indicates the rules or conditions governing when and how pit stops must be performed in a race or similar process.
-
B.
pitStopsRequired
chosen
Indicates that a process, journey, or operation necessitates one or more scheduled pit stops to be completed.
-
C.
maintenanceRequirement
Indicates that an entity is obligated to perform, schedule, or adhere to specific maintenance activities or conditions for another entity or system.
-
D.
requiresParkTicket
Indicates that access to something is conditional on possessing a valid park ticket.
-
E.
parkingRequirement
Indicates the specified conditions or obligations related to providing or using parking associated with an entity or activity.
- 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_69e24600eed08190bd7e5295653a1503 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd971d08190a132d24094e0c37b |
completed | April 29, 2026, 4:58 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:06 p.m.