Triple
T18064733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daewoo |
E432266
|
entity |
| Predicate | brandRetiredIn |
P46539
|
FINISHED |
| Object | many markets by 2011 |
—
|
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: many markets by 2011 | Statement: [Daewoo, brandRetiredIn, many markets by 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandRetiredIn Context triple: [Daewoo, brandRetiredIn, many markets by 2011]
-
A.
brandDiscontinuedAfter
Indicates that a brand ceased to exist or operate after a specified time or event.
-
B.
brandDiscontinuationYear
chosen
Indicates the year in which a brand ceased operations or was officially discontinued.
-
C.
brandMergedWith
Indicates that two previously distinct brands have combined into a single unified brand entity, typically through merger or acquisition.
-
D.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
E.
brandRevivedBy
Indicates that a previously inactive, discontinued, or defunct brand has been brought back into use or reintroduced by a specific agent or entity.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4cce74a0c81908375e3100c7578b8 |
completed | April 19, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.