Triple
T31038237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hang Seng TECH Index |
E790909
|
entity |
| Predicate | singleStockWeightCap |
P171122
|
FINISHED |
| Object | 8% |
—
|
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: 8% | Statement: [Hang Seng TECH Index, singleStockWeightCap, 8%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleStockWeightCap Context triple: [Hang Seng TECH Index, singleStockWeightCap, 8%]
-
A.
isMarketCapConstrained
Indicates that an entity’s market capitalization is subject to a specified limit or constraint.
-
B.
maximumTonnageLimitedBy
Indicates that the maximum allowable tonnage of one entity is constrained or capped by the capacity or limit specified by another entity.
-
C.
isMarketCapWeighted
Indicates that something (typically an index or portfolio) is constructed or allocated in proportion to the market capitalization of its constituent entities.
-
D.
hasMaximumBalanceLimit
Indicates that there is an upper bound on the balance that an account or entity is allowed to hold.
-
E.
weightLimitInPounds
Indicates the maximum allowable weight for something, expressed in pounds.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 8:59 p.m.