Triple
T30066166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaromír Jágr |
E764034
|
entity |
| Predicate | roleAtRytířiKladno |
P172171
|
FINISHED |
| Object | player-owner |
—
|
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: player-owner | Statement: [Jaromír Jágr, roleAtRytířiKladno, player-owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtRytířiKladno Context triple: [Jaromír Jágr, roleAtRytířiKladno, player-owner]
-
A.
roleOnGR20
Indicates the specific function or position an entity holds in the context of the GR20 (e.g., within an activity, project, or system labeled GR20).
-
B.
roleOnRhodes
Indicates that an entity held a specific role, position, or function on the island of Rhodes.
-
C.
riderType
Indicates the category or role of a rider in relation to a ride, transport service, or vehicle (e.g., passenger, driver, courier).
-
D.
roleOnLine1
Indicates that an entity holds a specific role or function associated with the first line of a multi-line structure or sequence.
-
E.
roleAtOutwild
Indicates that an entity holds or performs a specific role or position within the organization or context named Outwild.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 29, 2026, 6:59 p.m.