Triple
T34439832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIST 30 |
E884065
|
entity |
| Predicate | isMajorIndexOn |
P6680
|
FINISHED |
| Object | Borsa Istanbul |
—
|
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: Borsa Istanbul | Statement: [BIST 30, isMajorIndexOn, Borsa Istanbul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorIndexOn Context triple: [BIST 30, isMajorIndexOn, Borsa Istanbul]
-
A.
isMajorIndexOf
chosen
Indicates that one entity serves as the primary or major index reference for locating, organizing, or identifying another entity.
-
B.
isMajorFor
Indicates that one entity serves as the primary field of academic specialization (major) for another entity, typically a student.
-
C.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
D.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
-
E.
isMajorAxisIn
Indicates that one entity serves as the major (longest) axis within or of another entity, such as a shape, object, or coordinate 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 1, 2026, 2 a.m.