Triple
T21752421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSRGY |
E536946
|
entity |
| Predicate | isLongOnlyInstrument |
P35951
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NSRGY, isLongOnlyInstrument, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLongOnlyInstrument Context triple: [NSRGY, isLongOnlyInstrument, true]
-
A.
isLongOnlyEligible
Indicates that an entity is permitted to take only long (buy) positions and is not allowed to establish short (sell) positions.
-
B.
isTradeOnly
Indicates that the item or entity can only be obtained, exchanged, or interacted with through trading and not by other means such as purchase, crafting, or direct acquisition.
-
C.
isLongWhen
Indicates that something has a relatively great length or duration when a specified condition or context holds.
-
D.
allowedInstrument
chosen
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
-
E.
hasInstitutionalInstrument
Indicates that an entity is associated with, uses, or is governed by a specific institutional instrument (such as a formal policy, agreement, or regulatory mechanism).
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8b8b9c8190b1f6a8bc25d69dbb |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.