Triple
T36153649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buhen |
E1045659
|
entity |
| Predicate | controlledTradeIn |
P198813
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Buhen, controlledTradeIn, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledTradeIn Context triple: [Buhen, controlledTradeIn, gold]
-
A.
describesTradeIn
Indicates a relationship where one party provides an item or asset in exchange for another item, asset, or value as part of a trade-in transaction.
-
B.
describesTradeIn
Indicates that one entity provides an item or asset as a trade-in toward acquiring another item or service.
-
C.
describesTradeIn
Indicates that one entity provides something of value to another entity as part of an exchange or transaction.
-
D.
tradedIn
Indicates that one entity has given up or exchanged another entity, typically as part of a transaction to obtain something else.
-
E.
tradeInvolves
Indicates that a trade or exchange relationship exists between the referenced entities, where goods, services, or value are transferred among them.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
| PDg | Predicate description generation | batch_69ff0b6a541c8190a6fa847552f3491f |
completed | May 9, 2026, 10:24 a.m. |
Created at: May 3, 2026, 4:08 p.m.