Triple
T25767602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motors Liquidation Company |
E648925
|
entity |
| Predicate | excludedFromSaleTo |
P34541
|
FINISHED |
| Object | General Motors Company |
—
|
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: General Motors Company | Statement: [Motors Liquidation Company, excludedFromSaleTo, General Motors Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludedFromSaleTo Context triple: [Motors Liquidation Company, excludedFromSaleTo, General Motors Company]
-
A.
cannotBeSoldBy
Indicates that one entity is not permitted or not allowed to sell another entity.
-
B.
excludedFrom
chosen
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
C.
notSoldIn
Indicates that a product or item is unavailable for purchase within a specified market, region, or sales channel.
-
D.
attemptedSaleTo
Indicates that one entity tried, but did not necessarily succeed, to sell something to another entity.
-
E.
exemptedFrom
Indicates that an entity is not subject to, or is formally released from, a rule, obligation, requirement, or liability that would otherwise apply.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 5:12 a.m.