Triple
T15872891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prefontaine Classic |
E384872
|
entity |
| Predicate | timingProvider |
P120855
|
FINISHED |
| Object | electronic timing |
—
|
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: electronic timing | Statement: [Prefontaine Classic, timingProvider, electronic timing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timingProvider Context triple: [Prefontaine Classic, timingProvider, electronic timing]
-
A.
timingStandard
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
B.
timingParameter
Indicates a relationship where one entity specifies or controls a temporal setting, constraint, or configuration parameter that determines the timing behavior of another entity or process.
-
C.
timingMethod
Indicates the method or technique used to measure or record the timing of an event or process.
-
D.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
E.
timingWithinService
Indicates that the timing of one event or action occurs entirely within the duration or validity period of a specified service.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:51 a.m.