Triple
T14564699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chery Automobile |
E341752
|
entity |
| Predicate | hasCKDAssembly |
P114699
|
FINISHED |
| Object | multiple overseas markets |
—
|
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: multiple overseas markets | Statement: [Chery Automobile, hasCKDAssembly, multiple overseas markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCKDAssembly Context triple: [Chery Automobile, hasCKDAssembly, multiple overseas markets]
-
A.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
B.
hasAssemblyLine
Indicates that one entity possesses or operates an assembly line used for producing or assembling items.
-
C.
hasAssemblyLineFor
Indicates that one entity operates or contains an assembly line specifically used to produce, process, or assemble another entity.
-
D.
hadLocalAssembly
Indicates that an entity hosted or possessed a local-level governing or decision-making assembly within its jurisdiction or area.
-
E.
assembledDuring
Indicates that one entity is put together or constructed within the time period of another event or process.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38c6350819091090ffd15772f6f |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:23 a.m.