Triple
T22336393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan L |
E552156
|
entity |
| Predicate | tradesOff |
P28908
|
FINISHED |
| Object | lower premiums for higher cost sharing |
—
|
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: lower premiums for higher cost sharing | Statement: [Plan L, tradesOff, lower premiums for higher cost sharing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradesOff Context triple: [Plan L, tradesOff, lower premiums for higher cost sharing]
-
A.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
B.
hasTradeoff
chosen
Indicates that one option or outcome involves a compromise in which gaining certain benefits requires accepting corresponding costs or disadvantages.
-
C.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
D.
tradeAspect
Indicates a relationship where one entity is associated with a specific aspect, feature, or dimension of a trade or commercial transaction.
-
E.
tradesDuring
Indicates that a trading activity or transaction occurs within a specified time period or during a particular event or session.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577f2f208190ac6270ac4581fa15 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.