Triple
T31591653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBY |
E806112
|
entity |
| Predicate | hasLotTradingUnit |
P103200
|
FINISHED |
| Object | share |
—
|
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: share | Statement: [BBY, hasLotTradingUnit, share]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLotTradingUnit Context triple: [BBY, hasLotTradingUnit, share]
-
A.
tradingLotUnit
chosen
Indicates the standard unit or quantity in which an asset or security is grouped and traded as a single lot.
-
B.
hasLotSize
Indicates that an entity possesses a specific amount or extent of physical area, typically referring to the size of a parcel of land or property lot.
-
C.
hasLotSizeType
Indicates the classification or category used to describe the size of a lot or parcel.
-
D.
tradingLot
Indicates the standard quantity or size of a financial instrument or commodity that is grouped together and traded as a single unit in a market transaction.
-
E.
hasUnitStructure
Indicates that an entity possesses a specific internal organization or arrangement that defines its structural composition.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 30, 2026, 10:28 p.m.