Triple
T31004924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobin tax |
E790040
|
entity |
| Predicate | isIntendedEffect |
P46826
|
FINISHED |
| Object | lengthen average holding period of currencies |
—
|
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: lengthen average holding period of currencies | Statement: [Tobin tax, isIntendedEffect, lengthen average holding period of currencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntendedEffect Context triple: [Tobin tax, isIntendedEffect, lengthen average holding period of currencies]
-
A.
hasIntendedEffect
chosen
Indicates that one entity is expected or designed to produce a particular effect or outcome on another entity or context.
-
B.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
C.
conditionalEffect
Indicates that one event, state, or action occurs or holds only if a specified condition is met.
-
D.
hasDirectEffect
Indicates that one entity produces an immediate and unmediated impact or change on another entity.
-
E.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 8:57 p.m.