Triple
T30013248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Václav Klement |
E762522
|
entity |
| Predicate | predecessorCompanyOf |
P37738
|
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: [Václav Klement, predecessorCompanyOf, Škoda Auto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorCompanyOf Context triple: [Václav Klement, predecessorCompanyOf, Škoda Auto]
-
A.
predecessorCompany
Indicates that one company previously existed in a role or form that was succeeded or replaced by another company.
-
B.
underlyingCompanyPredecessor
Indicates that one company served as a predecessor entity to another company in an underlying or foundational corporate relationship.
-
C.
formerParentCompany
Indicates that one entity previously served as the parent company of another but no longer holds that status.
-
D.
employerPredecessorName
Indicates that the referenced name identifies a previous employer of the entity in question.
-
E.
isCorporatePrecursorOf
chosen
Indicates that one corporate entity is a predecessor in the organizational or legal lineage of another corporate entity, such as through merger, acquisition, or reorganization.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 29, 2026, 6:45 p.m.