Triple
T13288799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HANS device |
E316510
|
entity |
| Predicate | introducedInSport |
P5086
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [HANS device, introducedInSport, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInSport Context triple: [HANS device, introducedInSport, late 20th century]
-
A.
introducedSport
Indicates that an entity caused a particular sport to be brought into use, practice, or awareness within a specific context or place.
-
B.
introducedAsWorldCupDisciplineIn
Indicates that a particular sport or event was officially added as a discipline in the World Cup in a specified year or edition.
-
C.
basedInSport
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
-
D.
usedInSport
chosen
Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
-
E.
firstAppearedInOlympics
Indicates the event or entity in which something made its debut appearance at the Olympic Games.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.