Triple
T29951738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurin & Klement FC |
E760784
|
entity |
| Predicate | isPredecessorBrandOf |
P113793
|
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: [Laurin & Klement FC, isPredecessorBrandOf, Škoda Auto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPredecessorBrandOf Context triple: [Laurin & Klement FC, isPredecessorBrandOf, Škoda Auto]
-
A.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
B.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
C.
successorBrandScope
chosen
Indicates that one brand has replaced or followed another brand in scope, such as in market presence, ownership, or official continuity.
-
D.
successorBrandOwner
Indicates that one brand owner has taken over ownership or control of a brand from a previous brand owner, acting as its legal or commercial successor.
-
E.
usesSameBrandFamilyAs
Indicates that two entities use products or services belonging to the same overarching brand family or brand portfolio.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6783586948190bbb1d9f27fba961a |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:26 p.m.