Triple
T5680662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nasdaq-100 futures |
E125189
|
entity |
| Predicate | positionLimitType |
P38256
|
FINISHED |
| Object | exchange-imposed position limits |
—
|
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: exchange-imposed position limits | Statement: [Nasdaq-100 futures, positionLimitType, exchange-imposed position limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionLimitType Context triple: [Nasdaq-100 futures, positionLimitType, exchange-imposed position limits]
-
A.
typeOfLimit
chosen
Indicates that one entity specifies the category or kind of limit that applies to another entity.
-
B.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
C.
outerLimitDefinedFrom
Indicates that the outer boundary or maximum extent of one entity is determined or specified based on another entity.
-
D.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
-
E.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.