Triple
T8150759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSE Composite Index |
E190325
|
entity |
| Predicate | isReferenceIndexFor |
P80829
|
FINISHED |
| Object | Chinese equity derivatives |
—
|
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: Chinese equity derivatives | Statement: [SSE Composite Index, isReferenceIndexFor, Chinese equity derivatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReferenceIndexFor Context triple: [SSE Composite Index, isReferenceIndexFor, Chinese equity derivatives]
-
A.
isComponentOfIndex
Indicates that something functions as a specific indexed component or element within a larger structured whole.
-
B.
isCompositeIndex
Indicates that an index is composed of multiple columns or fields combined into a single index structure.
-
C.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
D.
isReferencedIn
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
E.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4481f19c8190aeec9bf029ad321b |
completed | March 31, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39ba412881908a053e88f29a9588 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:37 p.m.