Triple
T26297045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobo Nia |
E661444
|
entity |
| Predicate | supportsMarginAdjustment |
P76247
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kobo Nia, supportsMarginAdjustment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMarginAdjustment Context triple: [Kobo Nia, supportsMarginAdjustment, yes]
-
A.
isMarginable
Indicates that a financial asset or position can be used as collateral for borrowing funds or trading on margin.
-
B.
adjustsFor
Indicates that one entity modifies, compensates, or accounts for the effects of another entity to achieve a corrected or normalized result.
-
C.
supportsAlignment
Indicates that one entity is compatible with and can properly function or operate in conjunction with a specified alignment, configuration, or standard.
-
D.
supportsMarginTrading
chosen
Indicates that one entity enables or allows another entity to engage in margin trading (trading with borrowed funds).
-
E.
margining
Indicates the process of posting, adjusting, or settling collateral (margin) between parties to secure obligations in a financial transaction or trading relationship.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 26, 2026, 10:13 p.m.