Triple
T36299093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvasiny |
E893454
|
entity |
| Predicate | hasKeyEmployer |
P192732
|
FINISHED |
| Object | Škoda Auto |
—
|
NE NERFINISHED |
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: Škoda Auto | Statement: [Kvasiny, hasKeyEmployer, Škoda Auto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyEmployer Context triple: [Kvasiny, hasKeyEmployer, Škoda Auto]
-
A.
hasAuthorEmployer
Indicates that the specified organization or entity is the employer of the author in question.
-
B.
namedForEmployer
Indicates that an entity is named after, or in honor of, its employer.
-
C.
hasTitleHolderEmployer
Indicates that an entity serving as a title holder is employed by or works for a particular employer.
-
D.
hasKeyOfWork
Indicates that one entity possesses or is associated with the key (tonal center) in which a work (such as a musical composition) is set.
-
E.
hasFatherEmployer
Indicates that the employer of a person’s father is related to or associated with that person.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
| PDg | Predicate description generation | batch_69fd28379d2c8190903ba228ee1cc756 |
completed | May 8, 2026, 12:03 a.m. |
Created at: May 3, 2026, 4:09 p.m.