Triple
T2028405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTSE All-Share Index |
E44461
|
entity |
| Predicate | isBroadMarketBenchmark |
P34714
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [FTSE All-Share Index, isBroadMarketBenchmark, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBroadMarketBenchmark Context triple: [FTSE All-Share Index, isBroadMarketBenchmark, true]
-
A.
isMajorUSIndex
Indicates that the subject is one of the primary, widely recognized stock market indices in the United States.
-
B.
isBlueChipIndex
Indicates that an index is composed primarily of large, well-established, financially stable companies considered blue-chip stocks.
-
C.
hasMajorMarket
Indicates that an entity has a primary or most significant market in a specified location or segment.
-
D.
isRegulatedMarket
Indicates that a market operates under formal legal or regulatory oversight and must comply with specific rules and standards set by an authority.
-
E.
isWidelyTraded
Indicates that an asset or item is frequently bought and sold across many participants or markets, resulting in high trading activity and liquidity.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9136f888190b0fd03530e9eda1e |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:38 p.m.