Triple
T11611730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Feeding Program |
E275399
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | SFP |
E203457
|
NE 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: SFP | Statement: [Supplementary Feeding Program, acronym, SFP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SFP Context triple: [Supplementary Feeding Program, acronym, SFP]
-
A.
SFP
chosen
SFP is a liberal-centrist political party in Finland that primarily represents the interests of the Swedish-speaking minority.
-
B.
XFP
XFP is a compact, hot-swappable 10 Gigabit optical transceiver module form factor commonly used in high-speed Ethernet and fiber-optic communication links.
-
C.
SFP9
The SFP9 is a modern 9mm semi-automatic striker-fired pistol produced by Heckler & Koch for law enforcement, military, and civilian use.
-
D.
SFF-8639
SFF-8639 is a high-speed connector and interface standard used primarily for U.2 NVMe solid-state drives in enterprise storage systems.
-
E.
SFF-8482
SFF-8482 is a standardized internal connector interface designed specifically for Serial Attached SCSI (SAS) drives, allowing compatibility with both SAS and SATA devices in enterprise storage systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a043a3c08190a20cbc2ba5a8d218 |
completed | April 10, 2026, 7:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e8a8311bcc8190a3fe7d28c593aea3 |
completed | April 22, 2026, 10:51 a.m. |
Created at: April 8, 2026, 9:38 p.m.