Triple
T24626959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Cavalier (China) |
E609567
|
entity |
| Predicate | hasExportVersion |
P24987
|
FINISHED |
| Object | Chevrolet Cavalier (Mexico) |
—
|
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: Chevrolet Cavalier (Mexico) | Statement: [Chevrolet Cavalier (China), hasExportVersion, Chevrolet Cavalier (Mexico)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExportVersion Context triple: [Chevrolet Cavalier (China), hasExportVersion, Chevrolet Cavalier (Mexico)]
-
A.
hasVersionIn
chosen
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
isExported
Indicates that an entity is sent out or transferred from its origin to an external destination or system.
-
C.
hasExportPort
Indicates that an entity possesses or is associated with a port through which goods, services, or data are exported.
-
D.
hasExportActivity
Indicates that an entity engages in exporting goods or services to other countries or external markets.
-
E.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.