Triple
T31651289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kostelić family |
E807736
|
entity |
| Predicate | memberPlaysRole |
P189728
|
FINISHED |
| Object | athlete |
—
|
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: athlete | Statement: [Kostelić family, memberPlaysRole, athlete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberPlaysRole Context triple: [Kostelić family, memberPlaysRole, athlete]
-
A.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
B.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
C.
holdersPlayedRoleIn
Indicates that the holders of something (e.g., a position, title, or asset) participated in or contributed to a particular role within an event, activity, or context.
-
D.
roleAtMatches
Indicates that an entity’s role or position at a given time or context matches a specified role criterion.
-
E.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: April 30, 2026, 10:53 p.m.