Triple
T34395014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIST |
E882804
|
entity |
| Predicate | listedInstrumentType |
P12711
|
FINISHED |
| Object | common stock |
—
|
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: common stock | Statement: [BIST, listedInstrumentType, common stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedInstrumentType Context triple: [BIST, listedInstrumentType, common stock]
-
A.
includesInstruments
Indicates that one entity contains, involves, or makes use of one or more instruments as part of its composition or execution.
-
B.
relatedInstrumentType
Indicates that one instrument is associated with or connected to another by type, such as being a variant, subtype, or closely related form.
-
C.
instruments
Indicates that an agent uses a tool, device, or means to carry out an action or achieve an effect.
-
D.
typeOfInstrument
chosen
Indicates the specific kind or category of instrument associated with an entity.
-
E.
instrumentsUsedBy
Indicates that a particular instrument, tool, or device is employed or utilized by a given entity to perform an action or achieve a result.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.