Triple
T260927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajon Rondo |
E5538
|
entity |
| Predicate | tradeDetails |
P2914
|
FINISHED |
| Object | draft rights traded to Boston Celtics in 2006 |
—
|
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: draft rights traded to Boston Celtics in 2006 | Statement: [Rajon Rondo, tradeDetails, draft rights traded to Boston Celtics in 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradeDetails Context triple: [Rajon Rondo, tradeDetails, draft rights traded to Boston Celtics in 2006]
-
A.
trades
chosen
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
B.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
C.
tradesInstrument
Indicates that one party engages in buying, selling, or exchanging a specified financial or tradable instrument.
-
D.
tradingStatus
Indicates the current state or condition of an entity’s ability to be traded or engaged in trading activities.
-
E.
marketType
Indicates the classification or category of market in which an entity operates or a transaction occurs (e.g., retail, wholesale, online).
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b6c968c819094fc903a3a377e15 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.