Triple
T26870542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairfield Sentry |
E676598
|
entity |
| Predicate | strategyDescribedAs |
P164297
|
FINISHED |
| Object | split-strike conversion |
—
|
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: split-strike conversion | Statement: [Fairfield Sentry, strategyDescribedAs, split-strike conversion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategyDescribedAs Context triple: [Fairfield Sentry, strategyDescribedAs, split-strike conversion]
-
A.
investmentStrategyDescribedAs
chosen
Indicates that an investment strategy is characterized or labeled using a particular description or term.
-
B.
strategyType
Indicates the specific kind or category of strategy associated with an entity or action.
-
C.
strategyDesigner
Indicates that one entity is responsible for creating or formulating strategies for another entity or context.
-
D.
strategyNote
Indicates that an entity is associated with a note or annotation describing a strategy, plan, or tactical approach related to it.
-
E.
styleDescribedAs
Indicates that the manner, aesthetic, or mode of something is characterized or labeled using a particular style description.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 27, 2026, 5:32 a.m.