Triple
T18141240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPSO |
E434267
|
entity |
| Predicate | canOffer |
P57109
|
FINISHED |
| Object | low-cost arbitration scheme |
—
|
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: low-cost arbitration scheme | Statement: [IPSO, canOffer, low-cost arbitration scheme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canOffer Context triple: [IPSO, canOffer, low-cost arbitration scheme]
-
A.
hasOffering
chosen
Indicates that one entity provides, presents, or makes available an offering (such as a product, service, or item) to another entity or context.
-
B.
usesOffering
Indicates that one entity makes use of, applies, or relies on a particular offering provided by another entity.
-
C.
cannotOffer
Indicates that one entity is unable or not permitted to provide, propose, or extend an offer to another entity.
-
D.
canGive
Indicates that one entity has the ability or permission to transfer something to another entity.
-
E.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de0b67308190ae3be2dbff99910a |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.