Triple
T14005375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPS-11 |
E336932
|
entity |
| Predicate | hasIncrementType |
P15959
|
FINISHED |
| Object | annual increment |
—
|
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: annual increment | Statement: [BPS-11, hasIncrementType, annual increment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIncrementType Context triple: [BPS-11, hasIncrementType, annual increment]
-
A.
usesIncrement
Indicates that one entity applies or relies on an increment operation or incremental value derived from another entity.
-
B.
isIncremental
Indicates that something progresses or changes in small, successive steps or increases over time.
-
C.
hasIndexType
Indicates that an entity is associated with a particular type or category of index used to organize, reference, or access it.
-
D.
hasDeltaType
chosen
Indicates that one entity is associated with a specific type or category of change (delta) relative to another entity or state.
-
E.
hasRateType
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed1d2548190bb46d6b7cba4ffde |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.