Triple
T26610663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American harness racing |
E667911
|
entity |
| Predicate | hasStartMethod |
P181115
|
FINISHED |
| Object | mobile starting gate |
—
|
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: mobile starting gate | Statement: [North American harness racing, hasStartMethod, mobile starting gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartMethod Context triple: [North American harness racing, hasStartMethod, mobile starting gate]
-
A.
hasStageStart
Indicates that a process, event, or workflow begins or enters a particular stage at a specified point or condition.
-
B.
hasStartSection
Indicates that one entity serves as the starting section or initial segment of another entity.
-
C.
hasStartPattern
Indicates that something begins with, or is characterized at its outset by, a specified pattern.
-
D.
hasRouteStart
Indicates that one entity serves as the starting point or origin location for a specified route associated with another entity.
-
E.
hasVariableStart
Indicates that something begins at a non-fixed or changeable point, rather than at a single predetermined starting value or position.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: April 27, 2026, 2:16 a.m.