Triple
T12479980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honor (historical) |
E298278
|
entity |
| Predicate | reasonForDivestment |
P10639
|
FINISHED |
| Object | impact of US sanctions on Huawei |
—
|
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: impact of US sanctions on Huawei | Statement: [Honor (historical), reasonForDivestment, impact of US sanctions on Huawei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDivestment Context triple: [Honor (historical), reasonForDivestment, impact of US sanctions on Huawei]
-
A.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
B.
divested
chosen
Indicates that one entity has sold off, relinquished, or otherwise disposed of ownership, control, or interest in another entity or asset.
-
C.
reasonForWithdrawal
Indicates the cause, motive, or circumstance that explains why a withdrawal occurred.
-
D.
reasonForNationalization
Indicates the underlying cause or justification for which an entity was nationalized by a state.
-
E.
reasonForDelisting
Indicates the specific cause or justification for which an item, entity, or record has been removed from a list or registry.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.