Triple
T3654054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMT |
E77487
|
entity |
| Predicate | hasLotSizeType |
P50716
|
FINISHED |
| Object | standard round lot of 100 shares |
—
|
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: standard round lot of 100 shares | Statement: [LMT, hasLotSizeType, standard round lot of 100 shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLotSizeType Context triple: [LMT, hasLotSizeType, standard round lot of 100 shares]
-
A.
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.
-
B.
hasRateType
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
-
C.
marginType
Indicates the type or category of margin applied in a given context, such as financial, layout, or safety margin.
-
D.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
E.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b9164c81908938a4338430d193 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adbae14d488190a6024548979c6faf |
completed | March 8, 2026, 6:07 p.m. |
Created at: March 8, 2026, 3:24 p.m.