Triple
T21423797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consumer Electronics Show |
E528501
|
entity |
| Predicate | isTradeOnly |
P143909
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Consumer Electronics Show, isTradeOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTradeOnly Context triple: [Consumer Electronics Show, isTradeOnly, true]
-
A.
isTradeable
Indicates that an entity can be bought, sold, or exchanged within a market or trading system.
-
B.
isTradeOriented
Indicates that an entity is primarily focused on commercial exchange, market activities, or trade-related objectives in its operations or behavior.
-
C.
isTradedLike
Indicates that one entity is exchanged, valued, or handled in markets in a manner similar to another entity.
-
D.
usedForTradeBetween
Indicates that something serves as a medium, instrument, or basis for trade or exchange between two or more parties.
-
E.
usedForTrading
Indicates that one entity serves as a medium, instrument, or item exchanged in commercial or barter transactions involving another entity.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8139ce848190b812d6d07f1bdef8 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:48 p.m.