Triple
T25026493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakarta Composite Index |
E626722
|
entity |
| Predicate | hasSectorIndices |
P149159
|
FINISHED |
| Object | LQ45 Index |
—
|
NE NERFINISHED |
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: LQ45 Index | Statement: [Jakarta Composite Index, hasSectorIndices, LQ45 Index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSectorIndices Context triple: [Jakarta Composite Index, hasSectorIndices, LQ45 Index]
-
A.
hasSectorization
Indicates that one entity is divided into, assigned to, or associated with specific sectors defined by another entity.
-
B.
hasIndexSet
chosen
Indicates that something is associated with, defined over, or organized according to a particular set of indices.
-
C.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
D.
hasPlannedSectors
Indicates that an entity is associated with specific sectors that have been identified or designated in advance for future activity, development, or focus.
-
E.
hasIndexing
Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 6:07 a.m.