Triple
T6894543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indonesia Stock Exchange |
E159136
|
entity |
| Predicate | hasListedInstruments |
P72278
|
FINISHED |
| Object | equity securities |
—
|
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: equity securities | Statement: [Indonesia Stock Exchange, hasListedInstruments, equity securities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListedInstruments Context triple: [Indonesia Stock Exchange, hasListedInstruments, equity securities]
-
A.
includesInstruments
chosen
Indicates that one entity contains, involves, or makes use of one or more instruments as part of its composition or execution.
-
B.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
-
C.
allowedInstrument
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
-
D.
hasNotableInstrumentNamedAfter
Indicates that an entity has a notable musical instrument that is named after it.
-
E.
introducedInstrument
Indicates that one entity caused or brought about the initial use or adoption of a particular instrument by another entity or within a given context.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d931da24819096b9b205f2c0ebb0 |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.