Triple
T29951653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Václav Laurin |
E760781
|
entity |
| Predicate | notableEmployerSuccessor |
P207199
|
FINISHED |
| Object | Škoda Auto |
E39971
|
NE 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: Škoda Auto | Statement: [Václav Laurin, notableEmployerSuccessor, Škoda Auto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEmployerSuccessor Context triple: [Václav Laurin, notableEmployerSuccessor, Škoda Auto]
-
A.
notableSuccessor
Indicates that one entity is a prominent or historically significant successor to another in a sequence or lineage.
-
B.
hasCorporateSuccessor
Indicates that one corporate entity is the legal successor to another, inheriting its rights, obligations, or continuity of business.
-
C.
notableSuccessorFunction
Indicates that one entity is recognized as a significant or noteworthy successor to another in a sequence, role, or function.
-
D.
successorOfficeEstablished
Indicates that a new office or position was formally created to replace or succeed a previous one.
-
E.
notableSuccessorUnit
Indicates that one unit is recognized as a particularly significant or prominent successor to another unit in a sequence or lineage.
- F. None of above. chosen
Provenance (5 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27321cc74c819092a60b1168e57286 |
completed | June 8, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 6:26 p.m.