Triple
T31939093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunaújvárosi Acélbikák |
E815475
|
entity |
| Predicate | hasContactSport |
P31169
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dunaújvárosi Acélbikák, hasContactSport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactSport Context triple: [Dunaújvárosi Acélbikák, hasContactSport, yes]
-
A.
isContactSport
chosen
Indicates that the activity involves significant physical contact between participants as an inherent and expected part of play.
-
B.
hasSportsRole
Indicates that an entity holds or is assigned a specific role or position within a sports context or organization.
-
C.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
D.
performsAtSport
Indicates that an entity carries out or participates in an activity at a particular sport or sporting context.
-
E.
hasSportsOffered
Indicates that an entity provides or makes available certain sports as options or activities.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a033d975d788190aafc4be10d6c5c1c |
completed | May 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_6a033cc2668481908cb696e57632a68f |
completed | May 12, 2026, 2:44 p.m. |
Created at: May 1, 2026, 12:05 a.m.