Triple
T35330831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trackhouse Racing Team |
E1020310
|
entity |
| Predicate | hasPrimarySeries |
P72608
|
FINISHED |
| Object | NASCAR Cup Series |
E126946
|
NE 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: NASCAR Cup Series | Statement: [Trackhouse Racing Team, hasPrimarySeries, NASCAR Cup Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySeries Context triple: [Trackhouse Racing Team, hasPrimarySeries, NASCAR Cup Series]
-
A.
hasMainSeriesEntry
Indicates that an entity is a primary or canonical installment within a larger series or sequence of related works.
-
B.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
C.
hasStandardSeries
Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
-
D.
primarySeriesSupplied
Indicates that one entity provides or supplies the main or primary series associated with another entity.
-
E.
primarySeries
chosen
Indicates that one entity is the main or principal sequence, set, or collection to which another entity is related or belongs.
- F. None of above.
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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384a1b10148190a6ba3f0e616bf1c6 |
completed | June 21, 2026, 8:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.