Triple
T38190926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Ragan |
E1005456
|
entity |
| Predicate | racingLicense |
P19269
|
FINISHED |
| Object | NASCAR competition license |
—
|
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: NASCAR competition license | Statement: [David Ragan, racingLicense, NASCAR competition license]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: racingLicense Context triple: [David Ragan, racingLicense, NASCAR competition license]
-
A.
typeOfLicense
chosen
Indicates the specific kind or category of license associated with an entity.
-
B.
racingAchievement
Indicates that an entity has attained a notable result, record, or milestone in a competitive racing context.
-
C.
drivingRecord
Indicates the documented history of a person’s driving behavior, including past violations, accidents, and compliance with traffic laws.
-
D.
racingDriver
Indicates that one entity is a racing driver, i.e., a person who competes in motor races as a driver.
-
E.
hasLicense
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
- 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.